Removed prompt sign from code blocks

Author: nastena1606

.github/styles/config/vocabularies/Percona/accept.txt

@@ -23,3 +23,5 @@ MinIO
 [Rr]esync
 (?i)HMAC
 retryer
+Alibaba
+Alibaba Cloud

docs/details/authentication.md

@@ -17,13 +17,13 @@ etc. as the `mongo` shell or `mongodump` command does.
 
      The `pbm-agent` processes should connect to their localhost `mongod` with a standalone type of connection.
 
-     ```{.bash data-prompt="$"}
+     ```bash
      pbm-agent --mongodb-uri "mongodb://pbmuser:secretpwd@localhost:27017/?authSource=admin"
      ```
 
      Alternatively:
 
-     ```{.bash data-prompt="$"} 
+     ```bash 
      export PBM_MONGODB_URI="mongodb://pbmuser:secretpwd@localhost:27017/?authSource=admin"
      pbm-agent
      ```
@@ -32,15 +32,15 @@ etc. as the `mongo` shell or `mongodump` command does.
 
 === "The `pbm` CLI connection string"
 
-     ```{.bash data-prompt="$"}
+     ```bash
      pbm status --mongodb-uri "mongodb://pbmuser:secretpwd@mongocsvr1:27017,mongocsvr2:27017,mongocsvr3:27017/?replicaSet=configrs&authSource=admin"
      ```
 
      Alternatively:
 
-     ```{.bash data-prompt="$"}
+     ```bash
      export PBM_MONGODB_URI="mongodb://pbmuser:secretpwd@mongocsvr1:27017,mongocsvr2:27017,mongocsvr3:27017/?replicaSet=configrs&authSource=admin"
-     $ pbm status
+     pbm status
      ```
      
      Replace the `pbmuser:secretpwd` with the credentials of [the user who owns the pbm process](../install/configure-authentication.md#create-the-pbm-user)
@@ -86,28 +86,28 @@ Specify new values in MongoDB connection URI string as follows:
 
 === "The pbm-agent connection string"    
 
-    ```
+    ```bash
     pbm-agent --mongodb-uri "mongodb://pbmuser:secretpwd@localhost:27017/?authSource=admin&readConcernLevel=local&w=1"
     ```  
 
     Alternatively:    
 
-    ```
+    ```bash
     export PBM_MONGODB_URI="mongodb://pbmuser:secretpwd@localhost:27017/?authSource=admin&readConcernLevel=local&w=1"
     pbm-agent
     ```    
 
 === "The `pbm` CLI connection string"    
 
-    ```{.bash data-prompt="$"}
+    ```bash
     pbm status --mongodb-uri "mongodb://pbmuser:secretpwd@mongocsvr1:27017,mongocsvr2:27017,mongocsvr3:27017/?replicaSet=configrs&authSource=admin&readConcernLevel=local&w=1"
     ```    
 
     Alternatively:    
 
-    ```{.bash data-prompt="$"}
+    ```bash
     export PBM_MONGODB_URI="mongodb://pbmuser:secretpwd@mongocsvr1:27017,mongocsvr2:27017,mongocsvr3:27017/?replicaSet=configrs&authSource=admin&readConcernLevel=local&w=1"
-    $ pbm status
+    pbm status
     ```
 
 Supported values are:
@@ -131,14 +131,14 @@ For [Kerberos authentication :octicons-link-external-16:](https://docs.percona.c
 
 Specify the following string for MongoDB connection URI:
 
-```
+```bash
 PBM_MONGODB_URI="mongodb://<username>%40<KERBEROS_REALM>@<hostname>:27018/?authMechanism=GSSAPI&authSource=%24external&replSetName=xxxx"
 ```
 
 Note that you must first obtain the ticket for the `pbm` user with the `kinit` command before you start the **pbm-agent**:
 
-```{.bash data-prompt="$"}
-$ sudo -u {USER} kinit pbm
+```bash
+sudo -u {USER} kinit pbm
 ```
 
 Note that the `{USER}` is the user that you will run the `pbm-agent` process.
@@ -147,7 +147,7 @@ Note that the `{USER}` is the user that you will run the `pbm-agent` process.
 
 For [authentication and authorization via Native LDAP :octicons-link-external-16:](https://docs.percona.com/percona-server-for-mongodb/latest/authorization.html#authentication-and-authorization-with-direct-binding-to-ldap), you only create roles for LDAP groups in MongoDB as the users are stored and managed on the LDAP server. However, you still define the `$external` database as your authentication source:
 
-```
+```bash
 PBM_MONGODB_URI="mongodb://<user>:<password>@<hostname>:27017/?authMechanism=PLAIN&authSource=%24external&replSetName=xxxx"
 ```
 
@@ -170,7 +170,7 @@ When using [AWS IAM authentication :octicons-link-external-16:](https://docs.per
 
 The MongoDB connection URI string then looks like the following:
 
-```
+```bash
 PBM_MONGODB_URI="mongodb://<aws_access_key_id>:<aws_secret_access_key>@<hostname>:27017/?authMechanism=MONGODB-AWS&authSource=%24external&replSetName=xxxx"
 ```
 

docs/details/azure.md

@@ -26,32 +26,32 @@ For either method you need a storage account.
     1. Install the [Azure CLI :octicons-link-external-16:](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli). After the installation, the `az` is available for you.
     2. Sign in to Azure CLI:
 
-        ```{.bash data-prompt="$"}
-        $ az login
+        ```bash
+        az login
         ```
 
     3. Create a Resource group if it's not created for you:
 
-        ```{.bash data-prompt="$"}
-        $ az group create --name <your-resource-group> --location <your-location>
+        ```bash
+        az group create --name <your-resource-group> --location <your-location>
         ```
 
         For the list of available locations, run:
 
-        ```{.bash data-prompt="$"}
-        $ az account list-locations
+        ```bash
+        az account list-locations
         ```
 
     4. Create a storage account:
 
-        ```{.bash data-prompt="$"}
-        $ az storage account create --name <storage-account-name> --resource-group <your-resource-group> --location <your-location> --sku Standard_LRS
+        ```bash
+        az storage account create --name <storage-account-name> --resource-group <your-resource-group> --location <your-location> --sku Standard_LRS
         ```
 
     4. Create a blob container:
 
-        ```{.bash data-prompt="$"}
-        $ az storage container create --account-name <storage-account-name> --name <your-container>  --public-access off
+        ```bash
+        az storage container create --account-name <storage-account-name> --name <your-container>  --public-access off
         ```
 
         ??? example "Expected output"

docs/details/gcs.md

@@ -32,14 +32,14 @@ To use GCS, you need the following:
 
 2. Create a bucket
 
-    ```{.bash data-prompt="$"}
-    $ gcloud storage buckets create my-gcs-bucket --location=US
+    ```bash
+    gcloud storage buckets create my-gcs-bucket --location=US
     ```
 
 3. Verify the bucket creation
 
-    ```{.bash data-prompt="$"}
-    $ gcloud storage buckets list
+    ```bash
+    gcloud storage buckets list
     ```
 
 After the bucket is created, apply the proper [permissions for PBM to use the bucket](storage-configuration.md#permissions-setup).

docs/details/s3-storage.md

@@ -17,14 +17,14 @@ Here are some examples of the steps required to create a bucket.
 
     2. Create an S3 bucket
 
-       ```{.bash data-prompt="$"}
-       $ aws s3api create-bucket --bucket my-s3-bucket --region us-east-1
+       ```bash
+       aws s3api create-bucket --bucket my-s3-bucket --region us-east-1
        ```
       
     3. Verify the bucket creation
 
-        ```{.bash data-prompt="$"}
-        $ aws s3 ls
+        ```bash
+        aws s3 ls
         ```
         
 === ":simple-minio: MinIo"
@@ -33,20 +33,20 @@ Here are some examples of the steps required to create a bucket.
 
     2. Configure the `mc` command line tool with a MinIO Server
 
-        ```{.bash data-prompt="$"}
-        $ mc alias set myminio http://127.0.0.1:9000 MINIO_ACCESS_KEY MINIO_SECRET_KEY
+        ```bash
+        mc alias set myminio http://127.0.0.1:9000 MINIO_ACCESS_KEY MINIO_SECRET_KEY
         ```
 
     3. Create a bucket
 
-        ```{.bash data-prompt="$"}
-        $ mc mb myminio/my-minio-bucket
+        ```bash
+        mc mb myminio/my-minio-bucket
         ```
       
     4. Verify the bucket creation
 
-        ```{.bash data-prompt="$"}
-        $ mc ls myminio
+        ```bash
+        mc ls myminio
         ```
 
 After the bucket is created, apply the proper [permissions for PBM to use the bucket](storage-configuration.md#permissions-setup).
@@ -244,25 +244,25 @@ Let's assume that your custom CA certificate is at `/etc/ssl/minio-ca.crt` path
 
 2. Set the `SSL_CERT_FILE` environment variable to that file's path on each host where `pbm-agent` and PBM CLI are running:
 
-    ```{.bash data-prompt="$"}
-    $ export SSL_CERT_FILE=/etc/ssl/minio-ca.crt
+    ```bash
+    export SSL_CERT_FILE=/etc/ssl/minio-ca.crt
     ```
 
     If this variable isn't set, PBM uses the system root certificates.
 
 3. Restart `pbm-agent`:
 
-    ```{.bash data-prompt="$"}
-    $ sudo systemctl start pbm-agent
+    ```bash
+    sudo systemctl start pbm-agent
     ```
 
 4. Verify that your custom certificate is recognized. Check PBM logs for successful S3 access. 
 
 
 Alternatively, you can disable the TLS verification of the S3 storage in Percona Backup for MongoDB configuration:
 
-```{.bash data-prompt="$"}
-$ pbm config --set storage.s3.insecureSkipTLSVerify=True
+```bash
+pbm config --set storage.s3.insecureSkipTLSVerify=True
 ```
 
 !!! warning 

docs/features/multi-storage.md

@@ -38,14 +38,14 @@ storage:
 
 To upload the configuration profile to PBM, use the [`pbm profile add`](../reference/pbm-commands.md#pbm-profile-add) command and specify the path to the profile.
 
-```{.bash data-prompt="$"}
-$ pbm profile add <profile_name> /path/to/profile.yaml
+```bash
+pbm profile add <profile_name> /path/to/profile.yaml
 ```
 
 To show the information about the external backup storage, use the [`pbm profile show`](../reference/pbm-commands.md#pbm-profile-show) command:
 
-```{.bash data-prompt="$"}
-$ pbm profile show <profile_name>
+```bash
+pbm profile show <profile_name>
 ```
 
 See the full list of the configuration profile management commands in the [pbm commands](../reference/pbm-commands.md) reference.
@@ -54,8 +54,8 @@ See the full list of the configuration profile management commands in the [pbm c
 
 To make a backup to an external backup storage, pass the profile name with the `--profile` flag for the `pbm backup` command. For example, to run a physical backup and store it in the MinIO storage defined via the `minio` configuration profile, run the following command:
 
-```{.bash data-prompt="$"}
-$ pbm backup -t physical --profile=minio --wait 
+```bash
+pbm backup -t physical --profile=minio --wait 
 ```
 
 ??? example "Sample output"
@@ -76,8 +76,8 @@ Before you start, make sure that `pbm-agents` have the read permissions to backu
 
 1. List backups by running the `pbm list` or `pbm status` commands.
 
-    ```{.bash data-prompt="$"}
-	$ pbm list
+    ```bash
+	pbm list
 	```
 
 	The output shows the backup names and timestamps. External backups are marked with an asterisk:
@@ -96,8 +96,8 @@ Before you start, make sure that `pbm-agents` have the read permissions to backu
 
 2. To make a point-in-time restore, you must explicitly pass the backup name for the `pbm restore` command:
 
-    ```{.bash data-prompt="$"}
-    $ pbm-restore --time=<timestamp> --base-snapshot <backup-name>
+    ```bash
+    pbm-restore --time=<timestamp> --base-snapshot <backup-name>
     ```
 
 3. After the restore is complete, do the required post-restore steps depending on the restore type.
@@ -109,8 +109,8 @@ You can delete backups from an external storage only by name.
 
 Run the `pbm delete` command and pass the backup name:
 
-```{.bash data-prompt="$"}
-$ pbm delete-backup 2024-06-25T10:54:55Z
+```bash
+pbm delete-backup 2024-06-25T10:54:55Z
 ```
 
 ## Implementation specifics

docs/features/physical.md

@@ -156,8 +156,8 @@ To configure physical restores with a fallback directory, use either the PBM con
 
      You can start the restore with a fallback directory directly using the `--fallback-enabled` flag:
 
-     ```{.bash data-prompt="$"}
-     $ pbm restore --time <time> --fallback-enabled=true
+     ```bash
+     pbm restore --time <time> --fallback-enabled=true
      ```
 
 
@@ -172,8 +172,8 @@ A restore can succeed on most nodes, but it might fail on a few, resulting in a
 
 === ":material-console: Command line"
 
-    ```{.bash data-prompt="$"}
-    $ pbm restore --time <time> --fallback-enabled=true --allow-partly-done=true
+    ```bash
+    pbm restore --time <time> --fallback-enabled=true --allow-partly-done=true
     ```
        
 If you allow partial restores (default value), PBM finalizes the restore. Once the cluster is up and running, the failed node receives the necessary data from other members through an initial sync. 

docs/features/point-in-time-recovery.md

@@ -27,8 +27,8 @@ Set the `pitr.enabled` configuration option to `true`.
 
 === ":octicons-file-code-24: Command line"
 
-     ```{.bash data-prompt="$"}
-     $ pbm config --set pitr.enabled=true
+     ```bash
+     pbm config --set pitr.enabled=true
      ```
 
 === ":material-console: Configuration file"
@@ -87,8 +87,8 @@ You can change the duration of an oplog span via the configuration file. Specify
 
 === ":octicons-file-code-24: Command line"
 
-     ```{.bash data-prompt="$"}
-     $ pbm config --set pitr.oplogSpanMin=5
+     ```bash
+     pbm config --set pitr.oplogSpanMin=5
      ```
 
 === ":material-console: Configuration file"
@@ -157,8 +157,8 @@ The remaining secondaries and the primary nodes in the cluster receive priority
 
 To check the priorities, run the `pbm status` command with the  `--priority` flag.
 
-```{.bash data-prompt="$"}
-$ pbm status --priority
+```bash
+pbm status --priority
 ```
 
 ??? example "Sample output"
@@ -183,8 +183,8 @@ The oplog slices are saved with the `s2` compression method by default. You can
 
 === ":octicons-file-code-24: Command line"
 
-     ```{.bash data-prompt="$"}
-     $ pbm config --set pitr.compression=gzip
+     ```bash
+     pbm config --set pitr.compression=gzip
      ```
 
 === ":material-console: Configuration file"
@@ -214,8 +214,8 @@ The [`pbm list`](../reference/pbm-commands.md#pbm-list) output includes the foll
 * Valid time ranges for recovery
 * Point-in-time recovery status
 
-   ```{.bash data-prompt="$"}
-   $ pbm list
+   ```bash
+   pbm list
 
      2021-08-04T13:00:58Z [restore_to_time: 2021-08-04T13:01:23Z]
      2021-08-05T13:00:47Z [restore_to_time: 2021-08-05T13:01:11Z]