chore: updating the code block language identifier to have consistent…

… approach through the docs

localenv/README.md

@@ -129,7 +129,7 @@ If you want to start one local instance of Rafiki and peer it automatically to [
 
 // using Tigerbeetle DB
 
-```
+```sh
 pnpm localenv:compose:autopeer
 
 // OR using Postgres DB
@@ -298,7 +298,7 @@ Keep-Alive: timeout=5
 
 It is possible that upon (re)starting the local playground, you may run into an issue where there are no accounts/wallet addresses visible in the mock account servicing entities' pages (http://localhost:3030, http://localhost:3031). This is because seeding of the initial account data only works against an empty database. To correct this, clear the volumes, and restart the container via:
 
-```
+```sh
 pnpm localenv:compose down --volumes
 pnpm localenv:compose up -d
 ```

packages/documentation/src/content/docs/playground/autopeering.md

@@ -4,7 +4,7 @@ title: Auto-Peering
 
 If you want to start one local instance of Rafiki and peer it automatically to [Rafiki.money](https://rafiki.money), you can run the following commands:
 
-```
+```sh
 // using Tigerbeetle DB
 pnpm localenv:compose:autopeer
 
@@ -26,7 +26,7 @@ Note that you have to go through an additional "login" step by providing you IPv
 
 To shut down the connection and to clear the environment, run
 
-```
+```sh
 pnpm localenv:compose down --volumes
 ```
 

packages/documentation/src/content/docs/playground/overview.md

@@ -263,7 +263,7 @@ Keep-Alive: timeout=5
 
 It is possible that upon (re)starting the local playground, you may run into an issue where there are no accounts/wallet addresses visible in the mock account servicing entities' pages (http://localhost:3030, http://localhost:3031). This is because seeding of the initial account data only works against an empty database. To correct this, clear the volumes, and restart the container via:
 
-```
+```sh
 pnpm localenv:compose down --volumes
 pnpm localenv:compose up -d
 ```