Improvements

Author: montyly

program-analysis/echidna/advanced/using-all-contracts.md

@@ -2,20 +2,20 @@
 
 **Table of contents:**
 
-- [Understanding and using `allContracts` in Echidna](#understanding-and-using-allcontracts-in-echidna)
+- [Understanding and using `allContracts` in Echidna](#understanding-and-using-allContracts-in-echidna)
   - [Introduction](#introduction)
-  - [What is `allContracts` testing?](#what-is-allcontracts-testing)
-  - [When and how to use `allContracts`](#when-and-how-to-use-allcontracts)
+  - [What is `allContracts` testing?](#what-is-allContracts-testing)
+  - [When and how to use `allContracts`](#when-and-how-to-use-allContracts)
   - [Run Echidna](#run-echidna)
-    - [Example run with `allContracts` set to `false`](#example-run-with-allcontracts-set-to-false)
-    - [Example run with `allContracts` set to `true`](#example-run-with-allcontracts-set-to-true)
+    - [Example run with `allContracts` set to `false`](#example-run-with-allContracts-set-to-false)
+    - [Example run with `allContracts` set to `true`](#example-run-with-allContracts-set-to-true)
   - [Use cases and conclusions](#use-cases-and-conclusions)
 
 ## Introduction
 
 This tutorial is written as a hands-on guide to using `allContracts` testing in Echidna. You will learn what `allContracts` testing is, how to use it in your tests, and what to expect from its usage.
 
-**Important note**: this feature used to be called `multi-abi` but it was later renamed to `allContracts` in Echidna 2.1.0. As expected, this version or later is required for this tutorial.
+> This feature used to be called `multi-abi` but it was later renamed to `allContracts` in Echidna 2.1.0. As expected, this version or later is required for this tutorial.
 
 ## What is `allContracts` testing?
 
@@ -71,7 +71,7 @@ contract EchidnaTest {
 }
 ```
 
-Without using `allContracts` in a fuzzing campaign, Echidna is not able to break the invariant, because it only interacts with `EchidnaTest` functions. However, if we use the following configuration file, enabling `allContracts` testing, the invariant is broken. You can access [allContracts.yaml here](https://github.com/crytic/building-secure-contracts/blob/master/program-analysis/echidna/example/allContracts.yaml).
+In a non `allContracts` fuzzing campaign, Echidna is not able to break the invariant, because it only interacts with `EchidnaTest` functions. However, if we use the following configuration file, enabling `allContracts` testing, the invariant is broken. You can access [allContracts.yaml here](https://github.com/crytic/building-secure-contracts/blob/master/program-analysis/echidna/example/allContracts.yaml).
 
 ```yaml
 testMode: assertion
@@ -122,4 +122,4 @@ Testing with `allContracts` is a useful tool for complex systems that require th
 
 A side-effect of using `allContracts` is that the search space grows with the number of functions that can be called. This, combined with high values of sequence lengths, can make the fuzzing test not so thorough, because the dimension of the search space is simply too big to reasonably explore. Finally, adding more functions as fuzzing candidates makes the campaigns to take up more execution time.
 
-A final remark is that `allContracts` testing in assertion mode ignores all assert failures from the contracts not under test. This is shown in `Flag.test_fail()` function: even though it explicitly asserts false, the Echidna test ignores it.
+A final remark is that `allContracts` testing in assertion mode ignores all assert failures from the contracts not under test. This is shown in `Flag.test_fail()` function: even though it explicitly asserts false, the Echidna test ignores it.