minor wording changes

Author: tuturu-tech

program-analysis/README.md

@@ -16,7 +16,7 @@ Each technique has its advantages and pitfalls, making them useful in [specific
 
 \* if all paths are explored without timeout
 
-**Slither** analyzes contracts within seconds. However, static analysis might lead to false alarms and is less suitable for complex checks (e.g., arithmetic checks). Run Slither via the API for push-button access to built-in detectors or via the API for user-defined checks.
+**Slither** analyzes contracts within seconds. However, static analysis might lead to false alarms and is less suitable for complex checks (e.g., arithmetic checks). Run Slither via the CLI for push-button access to built-in detectors or via the API for user-defined checks.
 
 **Echidna** needs to run for several minutes and will only produce true positives. Echidna checks user-provided security properties written in Solidity. It might miss bugs since it is based on random exploration.
 
@@ -60,7 +60,7 @@ The broad areas frequently relevant for smart contracts include:
 
   - Manticore is the best choice here. Echidna can be used if the arithmetic is out-of-scope of the SMT solver.
 
-- **Inheritance correctness.** Solidity contracts rely heavily on multiple inheritance. Mistakes like a shadowing function missing a `super` call and misinterpreted c3 linearization order can quickly be introduced.
+- **Inheritance correctness.** Solidity contracts rely heavily on multiple inheritance. Mistakes like a shadowing function missing a `super` call and misinterpreted c3 linearization order can easily be introduced.
 
   - Slither is the tool for detecting these issues.
 

program-analysis/echidna/README.md

@@ -7,7 +7,7 @@ To learn through live coding sessions, watch our [Fuzzing workshop](https://www.
 **Table of Contents:**
 
 - [Introduction](introduction): Introductory material on fuzzing and Echidna
-- [Basic](basic): Discover the initial steps for using Echidna
+- [Basic](basic): Learn the first steps for using Echidna
 - [Advanced](advanced): Explore the advanced features of Echidna
 - [Fuzzing tips](./fuzzing_tips.md): General fuzzing recommendations
 - [Frequently Asked Questions](./frequently_asked_questions.md): Responses to common questions about Echidna

program-analysis/echidna/advanced/README.md

@@ -5,7 +5,7 @@
 - [How to Detect High Gas Consumption](./finding-transactions-with-high-gas-consumption.md): Find out how to identify functions with high gas consumption.
 - [How to Perform Large-scale Smart Contract Fuzzing](./smart-contract-fuzzing-at-scale.md): Explore how to use Echidna for long fuzzing campaigns on complex smart contracts.
 - [How to Test a Library](https://blog.trailofbits.com/2020/08/17/using-echidna-to-test-a-smart-contract-library/): Learn about using Echidna to test the Set Protocol library (blog post).
-- [How to Test Bytecode-only Contracts](./testing-bytecode.md): Learn how to fuzz contracts without bytecode or perform differential fuzzing between Solidity and Vyper.
+- [How to Test Bytecode-only Contracts](./testing-bytecode.md): Learn how to fuzz contracts without source code or perform differential fuzzing between Solidity and Vyper.
 - [How to Use Hevm Cheats to Test Permit](./hevm-cheats-to-test-permit.md): Find out how to test code that relies on ecrecover signatures by using hevm cheat codes.
-- [How to Seed Echidna with Unit Tests](./end-to-end-testing.md): Discover how to use existing unit tests as seeds for Echidna.
+- [How to Seed Echidna with Unit Tests](./end-to-end-testing.md): Discover how to use existing unit tests to seed Echidna.
 - [Understanding and Using `multi-abi`](./using-multi-abi.md): Learn what `multi-abi` testing is and how to utilize it effectively.

program-analysis/echidna/advanced/collecting-a-corpus.md

@@ -8,7 +8,7 @@
 
 ## Introduction
 
-In this guide, we will explore how to collect and use a corpus of transactions with Echidna. Our target is the following smart contract, _[magic.sol](https://github.com/crytic/building-secure-contracts/blob/master/program-analysis/echidna/example/magic.sol)_:
+In this guide, we will explore how to collect and use a corpus of transactions with Echidna. Our target is the following smart contract, [magic.sol](https://github.com/crytic/building-secure-contracts/blob/master/program-analysis/echidna/example/magic.sol):
 
 ```solidity
 contract C {
@@ -47,7 +47,7 @@ corpusDir: "corpus-magic"
 Now, run the tool and inspect the collected corpus:
 
 ```
-echidna-test magic.sol --config config.yaml
+echidna magic.sol --config config.yaml
 ```
 
 Echidna is still unable to find the correct magic value. To understand where it gets stuck, review the `corpus-magic/covered.*.txt` file:
@@ -130,7 +130,7 @@ cp corpus-magic/coverage/2712688662897926208.txt corpus-magic/coverage/new.txt
 Modify `new.txt` to call `magic(42,129,333,0)`. Now, re-run Echidna:
 
 ```
-echidna-test magic.sol --config config.yaml
+echidna magic.sol --config config.yaml
 ...
 echidna_magic_values: failed!💥
   Call sequence:

program-analysis/echidna/advanced/finding-transactions-with-high-gas-consumption.md

@@ -5,7 +5,7 @@
 - [Identifying high gas consumption transactions](#identifying-high-gas-consumption-transactions)
   - [Introduction](#introduction)
   - [Measuring Gas Consumption](#measuring-gas-consumption)
-- [Executing Echidna](#executing-echidna)
+- [Running Echidna](#running-echidna)
 - [Excluding Gas-Reducing Calls](#excluding-gas-reducing-calls)
   - [Summary: Identifying high gas consumption transactions](#summary-identifying-high-gas-consumption-transactions)
 
@@ -65,7 +65,7 @@ seqLen: 2
 estimateGas: true
 ```
 
-# Executing Echidna
+# Running Echidna
 
 With the configuration file created, we can run Echidna as follows:
 

program-analysis/echidna/advanced/optimization_mode.md

@@ -21,7 +21,7 @@ function echidna_opt_function() public view returns (int256) {
 
 ## Optimizing with Echidna
 
-In this example, the target is the following smart contract (_[opt.sol](https://github.com/crytic/building-secure-contracts/blob/master/program-analysis/echidna/example/opt.sol)_):
+In this example, the target is the following smart contract ([opt.sol](https://github.com/crytic/building-secure-contracts/blob/master/program-analysis/echidna/example/opt.sol)):
 
 ```solidity
 contract TestDutchAuctionOptimization {

program-analysis/echidna/advanced/using-multi-abi.md

@@ -33,7 +33,7 @@ This is where `multi-abi` testing comes in handy: It allows Echidna to call func
 
 We'll use a simple example to demonstrate how `multi-abi` works. We'll be using two contracts, `Flag` and `EchidnaTest`, both available in [multiabi.sol](https://github.com/crytic/building-secure-contracts/blob/master/program-analysis/echidna/example/multiabi.sol).
 
-The `Flag` contract contains a boolean flag that is only set if `flip()` is called, and a getter function returns the value of the flag. For now, ignore `test_fail()`; we'll discuss this function later.
+The `Flag` contract contains a boolean flag that is only set if `flip()` is called, and a getter function that returns the value of the flag. For now, ignore `test_fail()`; we'll discuss this function later.
 
 ```solidity
 contract Flag {

program-analysis/echidna/frequently_asked_questions.md

@@ -89,7 +89,7 @@ the path ends at the assert statement, so it should fail there.
 
 Coverage mappings can be imprecise; however, if they fail completely, it could be that you are using the [`viaIR` optimization option](https://docs.soliditylang.org/en/v0.8.14/ir-breaking-changes.html?highlight=viaIR#solidity-ir-based-codegen-changes), which appears to have some unexpected impact on the solc maps that we are still investigating. As a workaround, disable `viaIR`.
 
-## Echidna crashes, displaying "NonEmpty.fromList: empty list."
+## Echidna crashes, displaying "NonEmpty.fromList: empty list"
 
 Echidna relies on the Solidity metadata to detect where each contract is deployed. Please do not disable it. If this is not the case, please [open an issue](https://github.com/crytic/echidna/issues) in our issue tracker.