Merge pull request #9258 from MrJithil/clipboard-readme-file-issues-fix

Clipboard readme file issues fix

Author: corwintines

src/content/developers/docs/standards/tokens/erc-20/index.md

@@ -82,7 +82,7 @@ see below we will use a simplified ABI, to make it a low friction example.
 First, make sure you have installed [Web3.py](https://web3py.readthedocs.io/en/stable/quickstart.html#installation) Python library:
 
 ```
-$ pip install web3
+pip install web3
 ```
 
 ```python

src/content/developers/docs/standards/tokens/erc-721/index.md

@@ -77,7 +77,7 @@ see below we will use a simplified ABI, to make it a low friction example.
 First, make sure you have installed [Web3.py](https://web3py.readthedocs.io/en/stable/quickstart.html#installation) Python library:
 
 ```
-$ pip install web3
+pip install web3
 ```
 
 ```python

src/content/developers/tutorials/a-developers-guide-to-ethereum-part-one/index.md

@@ -83,19 +83,19 @@ In this walkthrough, we’ll just be working within a Python interpreter. We won
 First, install [IPython](https://ipython.org/) for a user-friendly environment to explore in. IPython offers tab completion, among other features, making it much easier to see what’s possible within Web3.py.
 
 ```bash
-$ pip install ipython
+pip install ipython
 ```
 
 Web3.py is published under the name `web3`. Install it like so:
 
 ```bash
-$ pip install web3
+pip install web3
 ```
 
 One more thing – we're going to simulate a blockchain later, which requires a couple more dependencies. You can install those via:
 
 ```bash
-$ pip install 'web3[tester]'
+pip install 'web3[tester]'
 ```
 
 You’re all set up to go!
@@ -105,7 +105,7 @@ You’re all set up to go!
 Open up a new Python environment by running `ipython` in your terminal. This is comparable to running `python`, but comes with more bells and whistles.
 
 ```bash
-$ ipython
+ipython
 ```
 
 This will print out some information about the versions of Python and IPython you’re running, then you should see a prompt waiting for input:

src/content/developers/tutorials/how-to-use-echidna-to-test-smart-contracts/index.md

@@ -133,13 +133,13 @@ We do not need any particular initialization in our current example, as a result
 Echidna is launched with:
 
 ```bash
-$ echidna-test contract.sol
+echidna-test contract.sol
 ```
 
 If contract.sol contains multiple contracts, you can specify the target:
 
 ```bash
-$ echidna-test contract.sol --contract MyContract
+echidna-test contract.sol --contract MyContract
 ```
 
 ### Summary: Testing a property {#summary-testing-a-property}
@@ -156,7 +156,7 @@ contract TestToken is Token{
 ```
 
 ```bash
-$ echidna-test testtoken.sol --contract TestToken
+echidna-test testtoken.sol --contract TestToken
 ...
 
 echidna_balance_under_1000: failed!💥
@@ -228,7 +228,7 @@ This is hard for a fuzzer (it is recommended to use a symbolic execution tool li
 We can run Echidna to verify this:
 
 ```bash
-$ echidna-test multi.sol
+echidna-test multi.sol
 ...
 echidna_state4: passed! 🎉
 Seed: -3684648582249875403
@@ -262,7 +262,7 @@ filterFunctions: ["f", "g", "h", "i"]
 To run Echidna with a configuration file `blacklist.yaml`:
 
 ```bash
-$ echidna-test multi.sol --config blacklist.yaml
+echidna-test multi.sol --config blacklist.yaml
 ...
 echidna_state4: failed!💥
   Call sequence:
@@ -284,7 +284,7 @@ filterFunctions: ["f1", "f2", "f3"]
 ```
 
 ```bash
-$ echidna-test contract.sol --config config.yaml
+echidna-test contract.sol --config config.yaml
 ...
 ```
 
@@ -337,7 +337,7 @@ checkAsserts: true
 When we run this contract in Echidna, we obtain the expected results:
 
 ```bash
-$ echidna-test assert.sol --config config.yaml
+echidna-test assert.sol --config config.yaml
 Analyzing contract: assert.sol:Incrementor
 assertion in inc: failed!💥
   Call sequence, shrinking (2596/5000):
@@ -404,7 +404,7 @@ contract Incrementor {
 ```
 
 ```bash
-$ echidna-test assert.sol --config config.yaml
+echidna-test assert.sol --config config.yaml
 Analyzing contract: assert.sol:Incrementor
 assertion in inc: failed!💥
   Call sequence, shrinking (2596/5000):
@@ -444,7 +444,7 @@ This small example forces Echidna to find certain values to change a state varia
 We can run Echidna to verify this:
 
 ```bash
-$ echidna-test magic.sol
+echidna-test magic.sol
 ...
 
 echidna_magic_values: passed! 🎉
@@ -459,7 +459,7 @@ However, we can still use Echidna to collect corpus when running this fuzzing ca
 To enable the corpus collection, create a corpus directory:
 
 ```bash
-$ mkdir corpus-magic
+mkdir corpus-magic
 ```
 
 And an [Echidna configuration file](https://github.com/crytic/echidna/wiki/Config) `config.yaml`:
@@ -472,7 +472,7 @@ corpusDir: "corpus-magic"
 Now we can run our tool and check the collected corpus:
 
 ```bash
-$ echidna-test magic.sol --config config.yaml
+echidna-test magic.sol --config config.yaml
 ```
 
 Echidna still cannot find the correct magic values, but we can take look to the corpus it collected.
@@ -529,13 +529,13 @@ Echidna needs some help in order to deal with the `magic` function. We are going
 parameters for it:
 
 ```bash
-$ cp corpus/2712688662897926208.txt corpus/new.txt
+cp corpus/2712688662897926208.txt corpus/new.txt
 ```
 
 We will modify `new.txt` to call `magic(42,129,333,0)`. Now, we can re-run Echidna:
 
 ```bash
-$ echidna-test magic.sol --config config.yaml
+echidna-test magic.sol --config config.yaml
 ...
 echidna_magic_values: failed!💥
   Call sequence:
@@ -583,7 +583,7 @@ Currently, Echidna always need a property to test: here `echidna_test` always re
 We can run Echidna to verify this:
 
 ```
-$ echidna-test gas.sol
+echidna-test gas.sol
 ...
 echidna_test: passed! 🎉
 
@@ -610,7 +610,7 @@ estimateGas: true
 Once we have the configuration file created, we can run Echidna like this:
 
 ```bash
-$ echidna-test gas.sol --config config.yaml
+echidna-test gas.sol --config config.yaml
 ...
 echidna_test: passed! 🎉
 
@@ -660,7 +660,7 @@ contract C {
 If Echidna can call all the functions, it won't easily find transactions with high gas cost:
 
 ```
-$ echidna-test pushpop.sol --config config.yaml
+echidna-test pushpop.sol --config config.yaml
 ...
 pop used a maximum of 10746 gas
 ...
@@ -680,7 +680,7 @@ filterFunctions: ["pop", "clear"]
 ```
 
 ```
-$ echidna-test pushpop.sol --config config.yaml
+echidna-test pushpop.sol --config config.yaml
 ...
 push used a maximum of 40839 gas
 ...
@@ -696,7 +696,7 @@ estimateGas: true
 ```
 
 ```bash
-$ echidna-test contract.sol --config config.yaml
+echidna-test contract.sol --config config.yaml
 ...
 ```
 

src/content/developers/tutorials/solidity-and-truffle-continuous-integration-setup/index.md

@@ -99,8 +99,8 @@ The eth-gas-reporter plugin is quite useful for keeping track of the gas costs o
 ### Step 1: Install the eth-gas-reporter plugin and codechecks {#step-1-install-the-eth-gas-reporter-plugin-and-codechecks}
 
 ```bash
-$ npm install --save-dev eth-gas-reporter
-$ npm install --save-dev @codechecks/client
+npm install --save-dev eth-gas-reporter
+npm install --save-dev @codechecks/client
 ```
 
 ### Step 2: Add the plugin to the mocha settings inside your truffle-config.js {#step-2-add-the-plugin-to-the-mocha-settings-inside-your-truffle-configjs}
@@ -151,9 +151,7 @@ With the solidity-coverage plugin you can check how much of your code paths are
 ### Step 1: Create a metacoin project and install coverage tools {#step-1-create-a-metacoin-project-and-install-coverage-tools}
 
 ```bash
-$ npm install --save-dev truffle
-$ npm install --save-dev coveralls
-$ npm install --save-dev solidity-coverage
+npm install --save-dev truffle coveralls solidity-coverage
 ```
 
 ### Step 2: Add solidity-coverage to the plugins array in truffle-config.js {#step-2-add-solidity-coverage-to-the-plugins-array-in-truffle-configjs}

src/content/developers/tutorials/using-websockets/index.md

@@ -27,7 +27,7 @@ The easiest way to test out WebSockets is to install a command line tool for mak
 _Note: if you have an Alchemy account you can replace `demo` with your own API key. [Sign up for a free Alchemy account here!](https://auth.alchemyapi.io/signup)_
 
 ```
-$ wscat -c wss://eth-mainnet.ws.alchemyapi.io/ws/demo
+wscat -c wss://eth-mainnet.ws.alchemyapi.io/ws/demo
 
 >  {"jsonrpc":  "2.0", "id": 0, "method":  "eth_gasPrice"}
 

src/content/developers/tutorials/waffle-dynamic-mocking-and-testing-calls/index.md

@@ -30,29 +30,29 @@ Why is dynamic mocking useful? Well, it allows us to write unit tests instead of
 Before we start we need to prepare a simple node.js project:
 
 ```bash
-$ mkdir dynamic-mocking
-$ cd dynamic-mocking
-$ mkdir contracts src
+mkdir dynamic-mocking
+cd dynamic-mocking
+mkdir contracts src
 
-$ yarn init
+yarn init
 # or if you're using npm
-$ npm init
+npm init
 ```
 
 Let's start with adding typescript and test dependencies - mocha & chai:
 
 ```bash
-$ yarn add --dev @types/chai @types/mocha chai mocha ts-node typescript
+yarn add --dev @types/chai @types/mocha chai mocha ts-node typescript
 # or if you're using npm
-$ npm install @types/chai @types/mocha chai mocha ts-node typescript --save-dev
+npm install @types/chai @types/mocha chai mocha ts-node typescript --save-dev
 ```
 
 Now let's add `Waffle` and `ethers`:
 
 ```bash
-$ yarn add --dev ethereum-waffle ethers
+yarn add --dev ethereum-waffle ethers
 # or if you're using npm
-$ npm install ethereum-waffle ethers --save-dev
+npm install ethereum-waffle ethers --save-dev
 ```
 
 Your project structure should look like this now:
@@ -108,7 +108,7 @@ It's time to build this contract! For that we will use `Waffle`. First, we're go
 Now we're ready to build the contract with Waffle:
 
 ```bash
-$ npx waffle
+npx waffle
 ```
 
 Easy, right? In `build/` folder two files corresponding to the contract and the interface appeared. We will use them later for testing.

src/content/translations/de/developers/docs/standards/tokens/erc-20/index.md

@@ -75,7 +75,7 @@ Sehen wir uns an, wie wichtig ein Standard ist, um uns die Überprüfung jedes E
 Stellen Sie zuerst sicher, dass Sie [Web3.py](https://web3py.readthedocs.io/en/stable/quickstart.html#installation) Python-Bibliothek installiert haben:
 
 ```
-$ pip install web3
+pip install web3
 ```
 
 ```python

src/content/translations/de/developers/docs/standards/tokens/erc-721/index.md

@@ -63,7 +63,7 @@ Lassen Sie uns sehen, wie wichtig ein Standard ist, um es uns einfach zu machen,
 Stellen Sie zuerst sicher, dass Sie [Web3.py](https://web3py.readthedocs.io/en/stable/quickstart.html#installation) Python-Bibliothek installiert haben:
 
 ```
-$ pip install web3
+pip install web3
 ```
 
 ```python

src/content/translations/es/developers/docs/standards/tokens/erc-20/index.md

@@ -75,7 +75,7 @@ Vamos a ver cómo un estándar es tan importante para que las cosas sean sencill
 Primero asegúrate de haber instalado [Web3.py](https://web3py.readthedocs.io/en/stable/quickstart.html#installation) Python library:
 
 ```
-$ pip install web3
+pip install web3
 ```
 
 ```python