Improve e2e docs

- Make newlines after heading consistent.
- Make navigation notation consistent.
- Use simpler code formatting, keep double backticks only where needed.
- Explain M1 Mac situation and link to corresponding issue.
- Reword a sentence to follow natural time sequence.
- Remove dot prefix from relative paths
    Paths with the dot appear as relative to the current file (e2e-web.md)
    but that's wrong. Remove the dot from relative paths forcing the reader
    to figure out what the path is relative to. Also note it at top of the
    manual.

docs/tests/e2e-web.md

@@ -2,48 +2,41 @@
 Suite uses [Cypress](https://docs.cypress.io/guides/overview/why-cypress.html) to run e2e tests. It also uses [trezor-user-env](https://github.com/trezor/trezor-user-env) which is [daily built](https://gitlab.com/satoshilabs/trezor/trezor-user-env/-/pipelines) into a docker image providing all the necessary instrumentation required to run tests (bridge and emulators).
 
 ## Run it locally
+_Note: All paths below are relative to the root of trezor-suite repository._
 
 ### On Linux
-
 #### Prerequisites
-
 - [Docker](https://docs.docker.com/docker-for-mac/install/)
 
 #### Steps
-
 1. Run `xhost +` to add yourself to the X access control list.
-2. Run `./docker/docker-suite-install.sh`.
-3. Run `./docker/docker-suite-test.sh`.
+2. Run `docker/docker-suite-install.sh`.
+3. Run `docker/docker-suite-test.sh`.
     - A Cypress window should open.
     - Wait until the project is built (a warning about "http://localhost:3000/ is not available", should disappear on the retry button click).
 4. Start a test by clicking its name in the Cypress window.
     - It should open a browser window.
     - If the Suite web app is not loading even after two retries. Stop tests, open a new tab, navigate to http://localhost:3000/, refresh the page until the app is loaded. Close the tab and run tests again.
 
 ### On MacOS
+As of now M1 Macs aren't supported. See [this issue](https://github.com/trezor/trezor-suite/issues/3616) for detailed information.
 
 #### Prerequisites
-
 - [Docker](https://docs.docker.com/docker-for-mac/install/)
 - [XQuartz](https://www.xquartz.org/) (to share your screen with Docker)
 
 #### Steps
-
-1. Run XQuartz. Leave it running on the background. Wait till it is launched.
-2. In XQuartz settings go to Preferences > Security and enable "Allow connections from network clients".
+1. Run XQuartz. Wait till it is launched. Leave it running in the background.
+2. In XQuartz settings go to Preferences -> Security and enable "Allow connections from network clients".
 3. Open a new terminal window (not in XQuartz) and add yourself to the X access control list: 
     - `xhost +127.0.0.1` 
     - You will probably need to logout/login after XQuartz installation to have `xhost` command available.
-4. Run Docker and go to Preferences->Resources->Advanced and increase RAM to at least 4GB. Otherwise, the app during tests does not even load.
-5. In terminal window run `./docker/docker-suite-install.sh`
+4. Run Docker and go to Preferences -> Resources -> Advanced and increase RAM to at least 4GB. Otherwise, the app during tests does not even load.
+5. In terminal window run `docker/docker-suite-install.sh`
 6. In the terminal window, set two environment variables:
-    - ``
-export HOSTNAME=`hostname`
-``
-    - ``
-export DISPLAY=${HOSTNAME}:0
-``
-7. In terminal window run `./docker/docker-suite-test.sh`
+    - `` export HOSTNAME=`hostname\` ``
+    - `export DISPLAY=${HOSTNAME}:0`
+7. In terminal window run `docker/docker-suite-test.sh`
     - A Cypress window should open.
     - Wait until the project is built (a warning about "http://localhost:3000/ is not available", should disappear on the retry button click).
 8. Start a test by clicking its name in the Cypress window.
@@ -54,25 +47,19 @@ export DISPLAY=${HOSTNAME}:0
 - `[...ERROR:browser_main_loop.cc(1434)] Unable to open X display.`
     - Make sure the XQuartz app is launched and you can see its terminal.
     - Check that environment variables are properly set:
-      - ``
-echo $HOSTNAME # e.g. name.local
-``
-      - ``
-echo $DISPLAY # e.g. name.local:0
-``
+        - `echo $HOSTNAME # e.g. name.local`
+        - `echo $DISPLAY # e.g. name.local:0`
     - Do not mix native terminal window with terminal window in your IDE (e.g. Visual Studio Code).
 
 ## Notes
-
 ### Image snapshots
-
 It is possible to run tests with image snapshots to test for visual regressions. To enable snapshots, use env variable:
 
-`CYPRESS_SNAPSHOT=1 ./docker/docker-suite-test.sh`
+`CYPRESS_SNAPSHOT=1 docker/docker-suite-test.sh`
 
 When you need to update image snapshots you have 2 options:
 - use CI job. This will generate new snapshots in artifacts together with a handy script that updates your snapshots locally. Check the log output. 
-- use `./docker/docker-suite-snapshots.sh`. This does the same as `./docker/docker-suite-test.sh`, the only difference is it won't fail on non-matching snapshots but generate new snapshots.
+- use `docker/docker-suite-snapshots.sh`. This does the same as `docker/docker-suite-test.sh`, the only difference is it won't fail on non-matching snapshots but generate new snapshots.
 
 ### run_tests script
 The [run_tests.js script](https://github.com/trezor/trezor-suite/blob/develop/packages/integration-tests/projects/suite-web/run_tests.js)