Sync Master <> Dev

docs/src/Usage.md

@@ -88,7 +88,7 @@ slither . --filter-paths "openzepellin"
 Filter all the results only related to openzepellin.
 
 ```
-slither . --filter-paths "Migrations.sol|ConvertLib.sol"
+slither . --filter-paths "SafeMath.sol|ConvertLib.sol"
 ```
 
 Filter all the results only related to the file `SafeMath.sol` or `ConvertLib.sol`.

docs/src/detectors/Detector-Documentation.md

@@ -1371,7 +1371,7 @@ Detects variables that are written but never read and written again.
         }
     }
     ```
-    `a` is first asigned to `b`, and then to `c`. As a result the first write does nothing.
+    `a` is first assigned to `b`, and then to `c`. As a result the first write does nothing.
 
 ### Recommendation
 

docs/src/printers/Printer-documentation.md

@@ -51,7 +51,7 @@ $ slither examples/printers/call_graph.sol --print call-graph
 <img src="https://raw.githubusercontent.com/crytic/slither/master/examples/printers/call_graph.sol.dot.png">
 
 The output format is [dot](https://www.graphviz.org/).
-To vizualize the graph:
+To visualize the graph:
 
 ```
 $ xdot examples/printers/call_graph.sol.dot
@@ -72,7 +72,7 @@ Export the control flow graph of each function
 ### Example
 
 The output format is [dot](https://www.graphviz.org/).
-To vizualize the graph:
+To visualize the graph:
 
 ```
 $ xdot function.sol.dot
@@ -355,7 +355,7 @@ INFO:PrinterInheritance:Inheritance Graph: examples/DAO.sol.dot
 ```
 
 The output format is [dot](https://www.graphviz.org/).
-To vizualize the graph:
+To visualize the graph:
 
 ```
 $ xdot examples/printers/inheritances.sol.dot

docs/src/tools/Code-Similarity-Detector.md

@@ -109,7 +109,7 @@ Here's an example to plot all the functions named `add` from contracts named `Sa
 ```
 $ slither-simil plot etherscan_verified_contracts.bin --fname SafeMath.add --input cache.npz --nsamples 500
 INFO:Slither-simil:Loading data..
-INFO:Slither-simil:Procesing data..
+INFO:Slither-simil:Processing data..
 INFO:Slither-simil:Plotting data..
 INFO:Slither-simil:Saving figure to plot.png..
 ```

docs/src/tools/Upgradeability-Checks.md

@@ -271,7 +271,7 @@ contract DerivedDerived is Derived{
 
 ```
 
-`Base.initialize(uint)` is called two times in `DerivedDerived.initiliaze` execution, leading to a potential corruption.
+`Base.initialize(uint)` is called two times in `DerivedDerived.initialize` execution, leading to a potential corruption.
 
 ### Recommendation
 

funding.json

@@ -1,5 +1,15 @@
 {
+    "Optimism": {
+        "op-mainnet": {
+            "ownedBy": "0xc44F30Be3eBBEfdDBB5a85168710b4f0e18f4Ff0"
+        }
+    },
+    "drips": {
+        "ethereum": {
+            "ownedBy": "0xc44F30Be3eBBEfdDBB5a85168710b4f0e18f4Ff0"
+        }
+    },
     "opRetro": {
         "projectId": "0xdc3dce33fd5fb50cf932586d4257456ddf5040ba0955d97641646504c73dbd13"
-    }
+  }
 }

slither/detectors/statements/pyth_unchecked.py

@@ -13,7 +13,7 @@ class PythUnchecked(AbstractDetector):
     Documentation: This detector finds deprecated Pyth function calls
     """
 
-    # To be overriden in the derived class
+    # To be overridden in the derived class
     PYTH_FUNCTIONS = []
     PYTH_FIELD = ""
 

slither/detectors/statements/write_after_write.py

@@ -86,7 +86,7 @@ def _detect_write_after_write(
 
     explored.add(node)
 
-    # We could report write after write for, but this lead to a lot of FP due to the initilization to zero pattern:
+    # We could report write after write for, but this lead to a lot of FP due to the initialization to zero pattern:
     # uint a = 0;
     # a = 10;
     # To do better, we could filter out if the variable is init to zero
@@ -123,7 +123,7 @@ class WriteAfterWrite(AbstractDetector):
         }
     }
     ```
-    `a` is first asigned to `b`, and then to `c`. As a result the first write does nothing."""
+    `a` is first assigned to `b`, and then to `c`. As a result the first write does nothing."""
     # endregion wiki_exploit_scenario
 
     WIKI_RECOMMENDATION = """Fix or remove the writes."""