docs: fix code blocks in CONTRIBUTING.md (#1162)

Author: alestiago

CONTRIBUTING.md

@@ -8,9 +8,9 @@ This project is opinionated and follows patterns and practices used by the team
 
 ## Understanding the Dart Frog repository
 
-This is a mono repo, a repository that includes more than one individual project. In fact, the Dart Frog repository includes all the packages, example apps, CLIs, and IDE integration plugins that have a role in the Dart Frog developer experience. 
+This is a mono repo, a repository that includes more than one individual project. In fact, the Dart Frog repository includes all the packages, example apps, CLIs, and IDE integration plugins that have a role in the Dart Frog developer experience.
 
-The contents of the mono repo is divided into the following directories: 
+The contents of the mono repo is divided into the following directories:
 
 - [`tool/`](https://github.com/VeryGoodOpenSource/dart_frog/tree/main/tool): contains internal operation scripts
 - [`assets/`](https://github.com/VeryGoodOpenSource/dart_frog/tree/main/assets): images to embed into READMEs
@@ -20,7 +20,7 @@ The contents of the mono repo is divided into the following directories:
 - [`bricks/`](https://github.com/VeryGoodOpenSource/dart_frog/tree/main/bricks): Internal mason bricks used by [dart_frog_cli][dart_frog_cli_link] to perform tasks such as creating new projects, starting a dev server, and building a prod server.
 - [`packages/`](https://github.com/VeryGoodOpenSource/dart_frog/tree/main/packages): The source code of the packages that constitute the Dart Frog suite (`dart_frog_cli`, `dart_frog` and `dart_frog_gen`) as well as companion packages (such as `dart_frog_web_socket`).
 
-Some of the included projects have more specific instructions on contribution. In these cases, the project root may include a `CONTRIBUTING.md` file with such instructions. 
+Some of the included projects have more specific instructions on contribution. In these cases, the project root may include a `CONTRIBUTING.md` file with such instructions.
 
 ## Proposing a changes & reporting bugs
 
@@ -62,46 +62,45 @@ Prerequisites:
 
 ### `dart_frog`
 
-This is the user-facing package of the Dart Frog SDK, which means that Dart Frog users will be using its API to construct servers and runtime operations. It contains logic for request parsing, middleware, and response creation. 
+This is the user-facing package of the Dart Frog SDK, which means that Dart Frog users will be using its API to construct servers and runtime operations. It contains logic for request parsing, middleware, and response creation.
 
 ### `dart_frog_gen`
 
-This is the internal package used by the Dart Frog tooling to interpret the file disposition and from it construct a Dart Frog server. 
+This is the internal package used by the Dart Frog tooling to interpret the file disposition and from it construct a Dart Frog server.
 
 > :warning: **Warning**: this package is a dependency on the bricks bundled into the CLI. This means that any changes that break the bricks should be released with a major version, otherwise dart frog users may be blocked from performing tasks such as `dev`, `build`, and `new`.
 
 ### `dart_frog_cli`
 
 A Dart command line interface package that serves as the main tool for Dart Frog. It includes bundled versions of the bricks under `bricks/`. To sync the source code of the bricks with new bundles, run `tool/generate_bundles.sh`.
 
-
 ### Companion packages
 
 The other items under `packages/` are companion packages in which dart_frog users may include on their project for specific server-side capabilities, such as auth (`dart_frog_auth`) and WebSockets (`dart_frog_web_socket`)
 
-
 ## Releasing versions of packages
 
 Before starting the release process of an individual package, first check:
 
 1. If your local `main` branch is up to date:
+
 ```shell
 # ☁️ Ensure you're up to date with the GitHub remote
 git checkout main
 git fetch
 git status
-/```
+```
 
 2. Ensure the [GitHub pipeline](https://github.com/VeryGoodOpenSource/dart_frog/actions) is green (has passed successfully) for your given package.
 
 3. Run the script under `tool/release_ready.sh` within the package root repository and the desired new version.
 
 ```shell
 # 🚀 Run the release ready script (from packages/<package>)
-../../tool/release_ready.sh <version> 
-/```
+../../tool/release_ready.sh <version>
+```
 
-The above example will: update the version of <package> to <version>, update the dart_frog CHANGELOG.md, create and checkout to a local release branch.
+The above example will: update the version of `<package>` to `<version>`, update the dart_frog CHANGELOG.md, create and checkout to a local release branch.
 
 4. Review the recently updated CHANGELOG file. You should manually amend the content were necessary. For example, by removing the redundant scope of some semantic pull requests or removing superfluous or unrelated logged changes.
 
@@ -111,7 +110,6 @@ The above example will: update the version of <package> to <version>, update the
 
 7. Open follow-up pull requests updating this package usage in any other Dart Frog package that depends on this new release.
 
-
 [conventional_commits_link]: https://www.conventionalcommits.org/en/v1.0.0
 [bug_report_link]: https://github.com/VeryGoodOpenSource/dart_frog/issues/new?assignees=&labels=bug&projects=&template=bug_report.md&title=fix%3A+
 [issue_creation_link]: https://github.com/VeryGoodOpenSource/dart_frog/issues/new/choose
@@ -122,4 +120,4 @@ The above example will: update the version of <package> to <version>, update the
 [mason_install_link]: https://docs.brickhub.dev/installing/
 [dart_standalone_link]: https://dart.dev/get-dart
 [dart_on_flutter_link]: https://docs.flutter.dev/get-started/install
-[github_release_link]:  https://github.com/VeryGoodOpenSource/dart_frog/releases
+[github_release_link]: https://github.com/VeryGoodOpenSource/dart_frog/releases