Update installation.md

doc/installation.md

@@ -112,22 +112,27 @@ We use the following tools to ensure consistent code style and formatting:
 We use [pre-commit](https://pre-commit.com/) so that its trivial to run the same linters & configuration locally as in CI.
 
 Run all linters liks:
-    ❯ pre-commit run --all-files
-    isort....................................................................Passed
-    black....................................................................Passed
-    mypy.....................................................................Passed
-
+```
+❯ pre-commit run --all-files
+isort....................................................................Passed
+black....................................................................Passed
+mypy.....................................................................Passed
+```
+
 Or run a single linter like:
-    ❯ pre-commit run --all-files isort
-    isort....................................................................Passed
+```
+❯ pre-commit run --all-files isort
+isort....................................................................Passed
+```
 
 Importantly, you can configure pre-commit to run automatically before every commit by running:
+```
+❯ pre-commit install --hook-type pre-commit
+pre-commit installed at .git/hooks/pre-commit
 
-    ❯ pre-commit install --hook-type pre-commit
-    pre-commit installed at .git/hooks/pre-commit
-
-    ❯ pre-commit install --hook-type pre-push
-    pre-commit installed at .git/hooks/pre-push
+❯ pre-commit install --hook-type pre-push
+pre-commit installed at .git/hooks/pre-push
+```
 
 This way you can ensure that you don't commit code style or formatting offenses.
 You can always temporarily skip the checks by using the `-n`/`--no-verify` git option.