fix typos in backup

docs/admin/20-getting-started/20-docker/20-docker-compose.md

@@ -2,7 +2,7 @@
 sidebar_position: 2
 id: docker-compose
 title: Docker Compose
-description: "🌟 Full-blown featureset including web office and full-text search."
+description: "🌟 Full-blown featureset including web office."
 ---
 
 # OpenCloud with Docker Compose

docs/admin/40-maintenance/20-backup.md

@@ -14,9 +14,9 @@ title: "Backup"
 
 - Pure POSIX Setup: All data (configuration, blobs, and metadata) is stored on a POSIX-compliant filesystem.
 
-- Distributed Setup: Blobs are stored on an S3-compliant storage, while configuration and metadata remain on a POSIX-compliant filesystem.
+- Distributed Setup: Blobs are stored on an S3-compliant storage, while configuration and metadata remain on a POSIX-compliant filesystem
 
-To determine which filesystems are supported, see: Filesystems and Shared Storage.
+To determine which filesystems are supported, see: Filesystems and Shared Storage
 
 ---
 
@@ -28,15 +28,15 @@ To determine which filesystems are supported, see: Filesystems and Shared Storag
 
 - Snapshot-based backup (recommended)
 
-    - If your storage system supports snapshots, creating a backup only takes a few seconds.
+    - If your storage system supports snapshots, creating a backup only takes a few seconds
 
-    - Snapshots should be copied to secondary storage or used by backup software for additional security.
+    - Snapshots should be copied to secondary storage or used by backup software for additional security
 
 -Backup software approach
 
-    - If snapshots are not available, you can use any backup software of your choice.
+    - If snapshots are not available, you can use any backup software of your choice
 
-    - For more details on data locations, refer to the Default Paths documentation.
+    - For more details on data locations, refer to the Default Paths documentation
 
 ---
 
@@ -60,37 +60,37 @@ To determine which filesystems are supported, see: Filesystems and Shared Storag
 
 - The configuration files
 
-- This ensures compatibility when restoring and prevents issues caused by software version mismatches.
+- This ensures compatibility when restoring and prevents issues caused by software version mismatches
 
 ---
 
 ### Pure POSIX setup
 
 #### If all data (configuration, blobs, and metadata) is stored on a POSIX-compliant filesystem:
 
-- Stop the OpenCloud instance.
+- Stop the OpenCloud instance
 
-- Create a backup of all data sets.
+- Create a backup of all data sets
 
-- If everything is on one filesystem, this is straightforward.
+- If everything is on one filesystem, this is straightforward
 
-- If separate filesystems are used for configuration and blobs/metadata, back up each one individually.
+- If separate filesystems are used for configuration and blobs/metadata, back up each one individually
 
-- Restart the OpenCloud instance after the backup is complete.
+- Restart the OpenCloud instance after the backup is complete
 
 ---
 
 ### Distributed setup
 
 #### If blobs are stored on S3, while configuration and metadata remain on a POSIX-compliant filesystem:
 
-- Stop the OpenCloud instance.
+- Stop the OpenCloud instance
 
-- Back up the configuration and metadata.
+- Back up the configuration and metadata
 
-- Back up the S3 bucket according to the guidelines of your S3 provider.
+- Back up the S3 bucket according to the guidelines of your S3 provider
 
-- Restart the OpenCloud instance after the backup is complete.
+- Restart the OpenCloud instance after the backup is complete
 
 ---