Reset readme changes

Author: ArayB

README.md

@@ -1,41 +1,33 @@
 # cp-zen-frontend
-
 Frontend code for the CoderDojo Community Platform (Zen)
 
 # Running e2e tests
 
 ## cypress tests
-
 We've begun moving e2e tests to [Cypress](https://www.cypress.io/) in order to improve reliability.
 
 ### Running with UI
-
-To run Cypress tests with the Cypress UI (good for debugging issues), you will first need to run the front end by running `yarn start`, then simply run.
-
+To run Cypress tests with the Cypress UI (good for debugging issues), you will first need to run the front end by running `yarn start`, then simply run
 ```
 yarn cypress:open
 ```
 
 This will open a window where you can select what spec to run. Notice that if you have a new version of the translations which is not published yet, tests on strings containing interpolation will fail as they are not depending on the linked version of your own repo. Running it headless will solve that.
 
 ### Headless
-
 You can also run the Cypress tests headless through Docker. You'll first need to install Cypress within the Docker container by running
-
 ```
 docker-compose run --rm cypress yarn cypress:install
 ```
 
 Once done, the installed Cypress is kept in a volume so it will persist between runs. If running the tests ever gives out about Cypress not being installed, just run this command again.
 
 To run the tests
-
 ```
 docker-compose run --rm cypress
 ```
 
 ### E2E Tests
-
 The tests in the `/cypress/integration_e2e` folder that are not run as part of the main test in CI.
 
 They are designed to be run manually & locally with the full stack, no endpoints are stubbed.
@@ -47,10 +39,9 @@ yarn cypress:e2e:open
 ```
 
 ## wdio tests
-
 The selenium-based wdio tests are legacy tests, waiting to be migrated to cypress. They are not actively maintained and are there only for reference until migrated.
 To run the tests
-
 ```
 docker-compose run --rm test e2e-with-mocks
 ```
+