fix: apply suggested changes

Author: AnnsAnns

doc/guides/rust_tutorials/rust_in_riot.md

@@ -118,7 +118,7 @@ and placing an `extern crate rust_riotmodules,` statement in the code.
 (The latter is needed even after most `extern crate` was abolished in 2018,
 because crates depended on but not used otherwise are usually not linked in).
 
-## Toolchain {#toolchain}
+## Toolchain
 
 Using Rust on RIOT needs the latest stable version of Rust. Please note that
 many popular Linux distributions provide very old versions in their
@@ -128,8 +128,8 @@ on its project website].
 
 Make sure you have the core library for the CPU (**target**) of your choice available:
 
-```
-$ rustup target add thumbv7m-none-eabi
+```shell
+rustup target add thumbv7m-none-eabi
 ```
 
 Substitute `thumbv7m-none-eabi` with the value of `RUST_TARGET`
@@ -145,8 +145,8 @@ To avoid playing the whack-a-mole of installing components whenever an install s
 consider installing this list of packages on Debian
 (or an equivalent list on the distribution of your choice):
 
-```
-# apt install libclang-dev llvm llvm-dev cmake libssl-dev pkg-config
+```shell
+apt install libclang-dev llvm llvm-dev cmake libssl-dev pkg-config
 ```
 
 This encompasses both components needed for riot-sys and for the later installation of C2Rust.
@@ -157,14 +157,14 @@ as this is using some recent fixes, it is best installed as:
 <!-- The locked works around <https://github.com/dtolnay/proc-macro2/issues/475> as closed in <https://github.com/immunant/c2rust/pull/1197>, there is no newer release that could be tested. -->
 
 ```shell
-$ cargo install c2rust --git https://github.com/immunant/c2rust --tag v0.19.0 --locked
+cargo install c2rust --git https://github.com/immunant/c2rust --tag v0.19.0 --locked
 ```
 
 If multiple versions of LLVM are installed locally,
 it may be necessary to prefix it with the selected LLVM version:
 
-```
-$ LLVM_CONFIG_PATH=/usr/bin/llvm-config-16 cargo install …
+```shell
+LLVM_CONFIG_PATH=/usr/bin/llvm-config-16 cargo install …
 ```
 
 [cargo]: https://doc.rust-lang.org/cargo/
@@ -192,8 +192,8 @@ The typical workflow of (C-nonbreaking, Rust-breaking) API changes is as follows
 
     Consequently, builds of Rust examples break.
 
+<!-- commit reference rather than PR as that was still on GitLab back then -->
 - A PR is opened on riot-wrappers to smooth over the change, like [aab605f4]
-<!-- commit reference rather than PR as that was still on GitLab back then -->.
 
     The PR is tested against current master in its CI (albeit not for the full set of boards).
     To test whether it also works for the changed API,