lint

Author: RidRisR

en/backup-to-aws-s3-using-br.md

@@ -1043,10 +1043,10 @@ The steps to prepare for a scheduled snapshot backup are the same as that of [Pr
     ```
 
     In the above example of `integrated-backup-schedule-s3.yaml`,  the `backupSchedule` configuration adds the `compactBackup` section based on the previous section. The key modifications are:
-    1. Added `BackupSchedule.spec.compactInterval` field: This allows specifying a custom interval for log compression backups. It is generally recommended to:
+    * Added `BackupSchedule.spec.compactInterval` field: This allows specifying a custom interval for log compression backups. It is generally recommended to:
       - Not exceed the scheduled snapshot backup interval
       - Set between one-half to one-third of the scheduled snapshot backup interval
-    2. Added `BackupSchedule.spec.compactBackupTemplate` field: 
+    * Added `BackupSchedule.spec.compactBackupTemplate` field: 
       - The `BackupSchedule.spec.compactBackupTemplate.S3` configuration must remain consistent with `BackupSchedule.spec.logBackupTemplate.S3`
 
 2. After creating `backupSchedule`, use the following command to check the backup status:
@@ -1060,7 +1060,7 @@ The steps to prepare for a scheduled snapshot backup are the same as that of [Pr
     ```shell
     kubectl get cpbk -n backup-test
     ```
-    
+
 ## Delete the backup CR
 
 If you no longer need the backup CR, refer to [Delete the Backup CR](backup-restore-overview.md#delete-the-backup-cr).

en/backup-to-azblob-using-br.md

@@ -888,10 +888,10 @@ The steps to prepare for a scheduled snapshot backup are the same as that of [Pr
     ```
 
     In the above example of `integrated-backup-schedule-azblob.yaml`,  the `backupSchedule` configuration adds the `compactBackup` section based on the previous section. The key modifications are:
-    1. Added `BackupSchedule.spec.compactInterval` field: This allows specifying a custom interval for log compression backups. It is generally recommended to:
+    * Added `BackupSchedule.spec.compactInterval` field: This allows specifying a custom interval for log compression backups. It is generally recommended to:
       - Not exceed the scheduled snapshot backup interval
       - Set between one-half to one-third of the scheduled snapshot backup interval
-    2. Added `BackupSchedule.spec.compactBackupTemplate` field: 
+    * Added `BackupSchedule.spec.compactBackupTemplate` field: 
       - The `BackupSchedule.spec.compactBackupTemplate.azblob` configuration must remain consistent with `BackupSchedule.spec.logBackupTemplate.azblob`
 
 2. After creating `backupSchedule`, use the following command to check the backup status:

en/backup-to-gcs-using-br.md

@@ -851,10 +851,10 @@ The steps to prepare for a scheduled snapshot backup are the same as that of [Pr
     ```
 
     In the above example of `integrated-backup-schedule-gcs.yaml`,  the `backupSchedule` configuration adds the `compactBackup` section based on the previous section. The key modifications are:
-    1. Added `BackupSchedule.spec.compactInterval` field: This allows specifying a custom interval for log compression backups. It is generally recommended to:
+    * Added `BackupSchedule.spec.compactInterval` field: This allows specifying a custom interval for log compression backups. It is generally recommended to:
       - Not exceed the scheduled snapshot backup interval
       - Set between one-half to one-third of the scheduled snapshot backup interval
-    2. Added `BackupSchedule.spec.compactBackupTemplate` field: 
+    * Added `BackupSchedule.spec.compactBackupTemplate` field: 
       - The `BackupSchedule.spec.compactBackupTemplate.gcs` configuration must remain consistent with `BackupSchedule.spec.logBackupTemplate.gcs`
 
 2. After creating `backupSchedule`, use the following command to check the backup status: