Update code fences in READMEs

Configuration/src/ConfigurationProviders/README.md

@@ -17,7 +17,7 @@ This is an ASP.NET Core application that shows how to use various `IConfiguratio
 
 1. Start a Config Server [docker container](https://github.com/SteeltoeOSS/Samples/blob/main/CommonTasks.md)
 1. Run the sample
-   ```
+   ```shell
    dotnet run
    ```
 
@@ -32,12 +32,12 @@ This sample expects the config server to be backed by the `spring-cloud-samples`
 ### App deployment
 
 1. Login to your Cloud Foundry environment and target your org/space
-   ```
+   ```shell
    cf target -o your-org -s your-space
    ```
 1. Run the `cf push` command to deploy from source
    - When deploying to Windows, binaries must be built locally before push. Use the following commands instead:
-     ```
+     ```shell
      dotnet publish -r win-x64 --self-contained
      cf push -f manifest-windows.yml -p bin/Release/net8.0/win-x64/publish
      ```
@@ -50,7 +50,7 @@ YAML files for creating the needed resources are included with this project, and
 but you are encouraged to review and/or customize the contents of the files before applying them.
 
 To create configuration objects (ConfigurationSource, ConfigurationSlice, ResourceClaim), run:
-```
+```shell
 kubectl config set-context --current --namespace=your-namespace
 kubectl apply -f ./config/application-configuration-service
 ```
@@ -60,12 +60,12 @@ For complete instructions, follow the [documentation](https://techdocs.broadcom.
 ### App deployment
 
 To deploy from local source code:
-```
+```shell
 tanzu app workload apply --local-path . --file ./config/workload.yaml -y
 ```
 
 Alternatively, from locally built binaries:
-```
+```shell
 dotnet publish -r linux-x64 --no-self-contained
 tanzu app workload apply --local-path ./bin/Release/net8.0/linux-x64/publish --file ./config/workload.yaml -y
 ```

Connectors/src/CosmosDb/README.md

@@ -12,7 +12,7 @@ for connecting to a CosmosDB database.
 1. Start the [Azure CosmosDB Emulator](https://learn.microsoft.com/azure/cosmos-db/how-to-develop-emulator)
 1. Update your local primary key in `appsettings.development.json` at `Steeltoe:Client:CosmosDb:Default:ConnectionString`
 1. Run the sample
-   ```
+   ```shell
    dotnet run
    ```
 

Connectors/src/MongoDb/README.md

@@ -17,7 +17,7 @@ for connecting to a MongoDB database.
 
 1. Start a MongoDB [docker container](https://github.com/SteeltoeOSS/Samples/blob/main/CommonTasks.md)
 1. Run the sample
-   ```
+   ```shell
    dotnet run
    ```
 
@@ -26,14 +26,14 @@ Upon startup, the app inserts a couple of objects into the bound MongoDB databas
 ## Running on Tanzu Platform for Cloud Foundry
 
 1. Create a MongoDB service instance in an org/space
-   ```
+   ```shell
    cf target -o your-org -s your-space
    cf create-service csb-azure-mongodb your-plan sampleMongoDbService
    ```
 1. Wait for the service to become ready (you can check with `cf services`)
 1. Run the `cf push` command to deploy from source (you can monitor logs with `cf logs mongodb-connector-sample`)
    - When deploying to Windows, binaries must be built locally before push. Use the following commands instead:
-     ```
+     ```shell
      dotnet publish -r win-x64 --self-contained
      cf push -f manifest-windows.yml -p bin/Release/net8.0/win-x64/publish
      ```
@@ -47,7 +47,7 @@ In order to connect to MongoDB for this sample, you must have a class claim avai
 The commands listed below will create the claim, and the claim will be bound to the application via the definition
 in the `workload.yaml` that is included in the `config` folder of this project.
 
-```
+```shell
 kubectl config set-context --current --namespace=your-namespace
 tanzu service class-claim create my-postgresql-service --class postgresql-unmanaged
 ```
@@ -58,12 +58,12 @@ and [consuming services](https://techdocs.broadcom.com/us/en/vmware-tanzu/standa
 ### App deployment
 
 To deploy from local source code:
-```
+```shell
 tanzu app workload apply --local-path . --file ./config/workload.yaml -y
 ```
 
 Alternatively, from locally built binaries:
-```
+```shell
 dotnet publish -r linux-x64 --no-self-contained
 tanzu app workload apply --local-path ./bin/Release/net8.0/linux-x64/publish --file ./config/workload.yaml -y
 ```

Connectors/src/MySql/README.md

@@ -24,7 +24,7 @@ There is also an additional sample that illustrates how to use Entity Framework
 
 1. Start a MySQL [docker container](https://github.com/SteeltoeOSS/Samples/blob/main/CommonTasks.md)
 1. Run the sample
-   ```
+   ```shell
    dotnet run
    ```
 
@@ -33,25 +33,25 @@ Upon startup, the app inserts a couple of rows into the bound MySQL database. Th
 ## Running on Tanzu Platform for Cloud Foundry
 
 1. Create a MySQL service instance in an org/space
-   ```
+   ```shell
    cf target -o your-org -s your-space
    ```
    - When using Tanzu for MySQL on Cloud Foundry:
-     ```
+     ```shell
      cf create-service p.mysql db-small sampleMySqlService
      ```
    - When using Tanzu Cloud Service Broker for GCP:
-     ```
+     ```shell
      cf create-service csb-google-mysql your-plan sampleMySqlService
      ```
    - When using Tanzu Cloud Service Broker for AWS:
-     ```
+     ```shell
      cf create-service csb-aws-mysql your-plan sampleMySqlService
      ```
 1. Wait for the service to become ready (you can check with `cf services`)
 1. Run the `cf push` command to deploy from source (you can monitor logs with `cf logs mysql-connector-sample`)
    - When deploying to Windows, binaries must be built locally before push. Use the following commands instead:
-     ```
+     ```shell
      dotnet publish -r win-x64 --self-contained
      cf push -f manifest-windows.yml -p bin/Release/net8.0/win-x64/publish
      ```
@@ -65,7 +65,7 @@ In order to connect to MySQL for this sample, you must have a class claim availa
 The commands listed below will create the claim, and the claim will be bound to the application via the definition
 in the `workload.yaml` that is included in the `config` folder of this project.
 
-```
+```shell
 kubectl config set-context --current --namespace=your-namespace
 tanzu service class-claim create my-postgresql-service --class postgresql-unmanaged
 ```
@@ -76,12 +76,12 @@ and [consuming services](https://techdocs.broadcom.com/us/en/vmware-tanzu/standa
 ### App deployment
 
 To deploy from local source code:
-```
+```shell
 tanzu app workload apply --local-path . --file ./config/workload.yaml -y
 ```
 
 Alternatively, from locally built binaries:
-```
+```shell
 dotnet publish -r linux-x64 --no-self-contained
 tanzu app workload apply --local-path ./bin/Release/net8.0/linux-x64/publish --file ./config/workload.yaml -y
 ```

Connectors/src/MySqlEFCore/README.md

@@ -23,7 +23,7 @@ There is also an additional sample that illustrates how to use a `MySqlConnectio
 
 1. Start a MySQL [docker container](https://github.com/SteeltoeOSS/Samples/blob/main/CommonTasks.md)
 1. Run the sample
-   ```
+   ```shell
    dotnet run
    ```
 
@@ -32,25 +32,25 @@ Upon startup, the app inserts a couple of rows into the bound MySQL database. Th
 ## Running on Tanzu Platform for Cloud Foundry
 
 1. Create a MySQL service instance in an org/space
-   ```
+   ```shell
    cf target -o your-org -s your-space
    ```
    - When using Tanzu for MySQL on Cloud Foundry:
-     ```
+     ```shell
      cf create-service p.mysql db-small sampleMySqlService
      ```
    - When using Tanzu Cloud Service Broker for GCP:
-     ```
+     ```shell
      cf create-service csb-google-mysql your-plan sampleMySqlService
      ```
    - When using Tanzu Cloud Service Broker for AWS:
-     ```
+     ```shell
      cf create-service csb-aws-mysql your-plan sampleMySqlService
      ```
 1. Wait for the service to become ready (you can check with `cf services`)
 1. Run the `cf push` command to deploy from source (you can monitor logs with `cf logs mysql-efcore-connector-sample`)
    - When deploying to Windows, binaries must be built locally before push. Use the following commands instead:
-     ```
+     ```shell
      dotnet publish -r win-x64 --self-contained
      cf push -f manifest-windows.yml -p bin/Release/net8.0/win-x64/publish
      ```
@@ -64,7 +64,7 @@ In order to connect to MySQL for this sample, you must have a class claim availa
 The commands listed below will create the claim, and the claim will be bound to the application via the definition
 in the `workload.yaml` that is included in the `config` folder of this project.
 
-```
+```shell
 kubectl config set-context --current --namespace=your-namespace
 tanzu service class-claim create my-postgresql-service --class postgresql-unmanaged
 ```
@@ -75,12 +75,12 @@ and [consuming services](https://techdocs.broadcom.com/us/en/vmware-tanzu/standa
 ### App deployment
 
 To deploy from local source code:
-```
+```shell
 tanzu app workload apply --local-path . --file ./config/workload.yaml -y
 ```
 
 Alternatively, from locally built binaries:
-```
+```shell
 dotnet publish -r linux-x64 --no-self-contained
 tanzu app workload apply --local-path ./bin/Release/net8.0/linux-x64/publish --file ./config/workload.yaml -y
 ```

Connectors/src/PostgreSql/README.md

@@ -24,7 +24,7 @@ There is also an additional sample that illustrates how to use Entity Framework
 
 1. Start a PostgreSQL [docker container](https://github.com/SteeltoeOSS/Samples/blob/main/CommonTasks.md)
 1. Run the sample
-   ```
+   ```shell
    dotnet run
    ```
 
@@ -33,25 +33,25 @@ Upon startup, the app inserts a couple of rows into the bound PostgreSQL databas
 ## Running on Tanzu Platform for Cloud Foundry
 
 1. Create a PostgreSQL service instance in an org/space
-   ```
+   ```shell
    cf target -o your-org -s your-space
    ```
    - When using Tanzu for Postgres on Cloud Foundry:
-     ```
+     ```shell
      cf create-service postgres small samplePostgreSqlService
      ```
    - When using Tanzu Cloud Service Broker for GCP:
-     ```
+     ```shell
      cf create-service csb-google-postgres your-plan samplePostgreSqlService
      ```
    - When using Tanzu Cloud Service Broker for AWS:
-     ```
+     ```shell
      cf create-service csb-aws-postgresql your-plan samplePostgreSqlService
      ```
 1. Wait for the service to become ready (you can check with `cf services`)
 1. Run the `cf push` command to deploy from source (you can monitor logs with `cf logs postgresql-connector-sample`)
    - When deploying to Windows, binaries must be built locally before push. Use the following commands instead:
-     ```
+     ```shell
      dotnet publish -r win-x64 --self-contained
      cf push -f manifest-windows.yml -p bin/Release/net8.0/win-x64/publish
      ```
@@ -65,7 +65,7 @@ In order to connect to PostgreSQL for this sample, you must have a class claim a
 The commands listed below will create the claim, and the claim will be bound to the application via the definition
 in the `workload.yaml` that is included in the `config` folder of this project.
 
-```
+```shell
 kubectl config set-context --current --namespace=your-namespace
 tanzu service class-claim create my-postgresql-service --class postgresql-unmanaged
 ```
@@ -76,12 +76,12 @@ and [consuming services](https://techdocs.broadcom.com/us/en/vmware-tanzu/standa
 ### App deployment
 
 To deploy from local source code:
-```
+```shell
 tanzu app workload apply --local-path . --file ./config/workload.yaml -y
 ```
 
 Alternatively, from locally built binaries:
-```
+```shell
 dotnet publish -r linux-x64 --no-self-contained
 tanzu app workload apply --local-path ./bin/Release/net8.0/linux-x64/publish --file ./config/workload.yaml -y
 ```

Connectors/src/PostgreSqlEFCore/README.md

@@ -23,7 +23,7 @@ There is also an additional sample that illustrates how to use a `NpgsqlConnecti
 
 1. Start a PostgreSQL [docker container](https://github.com/SteeltoeOSS/Samples/blob/main/CommonTasks.md)
 1. Run the sample
-   ```
+   ```shell
    dotnet run
    ```
 
@@ -32,25 +32,25 @@ Upon startup, the app inserts a couple of rows into the bound PostgreSQL databas
 ## Running on Tanzu Platform for Cloud Foundry
 
 1. Create a PostgreSQL service instance in an org/space
-   ```
+   ```shell
    cf target -o your-org -s your-space
    ```
    - When using Tanzu for Postgres on Cloud Foundry:
-     ```
+     ```shell
      cf create-service postgres small samplePostgreSqlService
      ```
    - When using Tanzu Cloud Service Broker for GCP:
-     ```
+     ```shell
      cf create-service csb-google-postgres your-plan samplePostgreSqlService
      ```
    - When using Tanzu Cloud Service Broker for AWS:
-     ```
+     ```shell
      cf create-service csb-aws-postgresql your-plan samplePostgreSqlService
      ```
 1. Wait for the service to become ready (you can check with `cf services`)
 1. Run the `cf push` command to deploy from source (you can monitor logs with `cf logs postgresql-efcore-connector-sample`)
    - When deploying to Windows, binaries must be built locally before push. Use the following commands instead:
-     ```
+     ```shell
      dotnet publish -r win-x64 --self-contained
      cf push -f manifest-windows.yml -p bin/Release/net8.0/win-x64/publish
      ```
@@ -64,7 +64,7 @@ In order to connect to PostgreSQL for this sample, you must have a class claim a
 The commands listed below will create the claim, and the claim will be bound to the application via the definition
 in the `workload.yaml` that is included in the `config` folder of this project.
 
-```
+```shell
 kubectl config set-context --current --namespace=your-namespace
 tanzu service class-claim create my-postgresql-service --class postgresql-unmanaged
 ```
@@ -75,12 +75,12 @@ and [consuming services](https://techdocs.broadcom.com/us/en/vmware-tanzu/standa
 ### App deployment
 
 To deploy from local source code:
-```
+```shell
 tanzu app workload apply --local-path . --file ./config/workload.yaml -y
 ```
 
 Alternatively, from locally built binaries:
-```
+```shell
 dotnet publish -r linux-x64 --no-self-contained
 tanzu app workload apply --local-path ./bin/Release/net8.0/linux-x64/publish --file ./config/workload.yaml -y
 ```