diff --git a/readme.md b/readme.md
index fac5f7e..7db928f 100644
--- a/readme.md
+++ b/readme.md
@@ -536,7 +536,7 @@ it("When visiting TestJavaScript.com home page, a menu is displayed", () => {
 
 <br/><br/>
 
-## ⚪ ️ 1.9 Copy code, but only what's neccessary
+## ⚪ ️ 1.9 Copy code, but only what's necessary
 
 :white_check_mark: **Do:** Include all the necessary details that affect the test result, but nothing more. As an example, consider a test that should factor 100 lines of input JSON - Pasting this in every test is tedious. Extracting it outside to transferFactory.getJSON() will leave the test vague - Without data, it's hard to correlate the test result with the cause ("why is it supposed to return 400 status?"). The classic book x-unit patterns named this pattern 'the mystery guest' - Something unseen affected our test results, we don't know what exactly. We can do better by extracting repeatable long parts outside AND mentioning explicitly which specific details matter to the test. Going with the example above, the test can pass parameters that highlight what is important: transferFactory.getJSON({sender: undefined}). In this example, the reader should immediately infer that the empty sender field is the reason why the test should expect a validation error or any other similar adequate outcome.
 <br/>
@@ -984,7 +984,7 @@ The second option is to clean up after all the test files have finished (or even
 
 <br/>
 
-### :clap: Cleaning after ALL the tests. Not neccesserily after every run. The more data we have while the tests are running - The more it resembles the production perks
+### :clap: Cleaning after ALL the tests. Not necessarily after every run. The more data we have while the tests are running - The more it resembles the production perks
 
 ```javascript
   // After-all clean up (recommended)