more linebreaks

README.md

@@ -16,21 +16,23 @@ This will be the default for running this lab. All exercises are described accor
 
 To run the lab on your local machine, you'll need to have [Docker](https://docs.docker.com/engine/install/), [VS Code](https://code.visualstudio.com/download), and the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) installed.
 When you open this repository with a locally installed VS Code instance, you'll see a prompt in the bottom right corner.
-<br />
+<br /><br />
 ![Prompt to open the repo inside a Dev container](tutorial/content/exercises/introduction/images/prompt.png)
 
 Press `Reopen in Container` to allow VS Code to use the [devcontainer.json](.devcontainer/devcontainer.json) specification to set up the IDE. If you missed the prompt hit <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd> (on Mac <kbd>Command</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd>) and type `Dev Containers: Rebuild and Reopen in Container`.
 
 After that the [devcontainer spec](.devcontainer.json) will pull all needed dependencies to build and run the devcontainer in which we will work on the lab content. This can take a bit, so be patient.
 
-<br />
+<br /><br />
 ![Open the terminal](tutorial/content/exercises/introduction/images/open-terminal.png)
 
 When you run an application that exposes a port, VS Code will notify you that it is accessible. 
 To open the application, just click `Open in Browser` or open your Browser manually and type the URL yourself.
+<br /><br />
 ![Open the browser](tutorial/content/exercises/introduction/images/open-port.png)
 
 When you missed the prompt you can see the open ports in the `PORTS` tab.
+<br /><br />
 ![Where to find the forwarded ports](tutorial/content/exercises/introduction/images/ports.png)
 
 ### Running the lab remotely
@@ -41,23 +43,23 @@ To utilize either option, you'll need a personal GitHub account.
 In both cases, a VSCode Instance in your browser will be opened automatically and you are immediately ready to go.
 
 Normally Codespaces and Gitpod should work in an almost identical way as a local devcontainer setup. However these platforms are subject to change and we can't keep the lab tested continously on all remote platforms.
-
+<br /><br />
 [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/NovatecConsulting/opentelemetry-training) [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/NovatecConsulting/opentelemetry-training)
 
 ###  Differences between local and remote way of running the lab
 
 Even though the experience with using a local or browser-based VS Code is fairly similar, one thing you need to take care of is the variation in hostnames and ports. In a local environment, you can use the combination of `localhost` and the corresponding port. In a remote environment, this will not work when trying to access endpoints via a browser.
 
 This is the ports tab of a local VS Code environment:
-
+<br /><br />
 ![VS Code ports](tutorial/content/exercises/introduction/images/vscode_ports.png)
 
 This is the ports tab of a GitHub Codespaces environment:
-
+<br /><br />
 ![Codespaces ports](tutorial/content/exercises/introduction/images/codespaces_ports.png)
 
 This is the ports tab of a GitHub Codespaces environment:
-
+<br /><br />
 ![Gitpod ports](tutorial/content/exercises/introduction/images/gitpod_ports.png)
 
 You can see that they look almost identical. In some cases, you might have to hover over the address to reveal a link.