From 7c4944e598715f59362451c347e95fae14c2ca2b Mon Sep 17 00:00:00 2001
From: Nicole Rappe <nicole.rappe@bunny-lab.io>
Date: Mon, 18 Nov 2024 00:03:43 -0700
Subject: [PATCH] Update Scripts/Powershell/rClone.md

---
 Scripts/Powershell/rClone.md | 21 +++++++++++----------
 1 file changed, 11 insertions(+), 10 deletions(-)

diff --git a/Scripts/Powershell/rClone.md b/Scripts/Powershell/rClone.md
index 70a33b0..c650542 100644
--- a/Scripts/Powershell/rClone.md
+++ b/Scripts/Powershell/rClone.md
@@ -15,17 +15,18 @@ Perform bidirectional synchronization between two paths.  Bisync provides a bidi
 ### Example Usage
 The following commands illustrate how to use bisync to synchronize a local folder and a remote folder (assumed to be Google Drive).  The `--drive-skip-gdocs` flag simply does not sync Google Drive specific documents back to the local folder, such as `*.gsheet`, `*.gdoc`, etc.  The `--resilient` flag means that if there are network interruptions, rclone will attempt to recover on its own automatically to resume where it last left off in the sync. 
 
-**Initial Sync**:
-You only run this command the first time you sync the local and remote locations.  It builds a database between the two locations to effectively "index" every file locally and remotely, so that subsequent syncs can track deletions, additions, and modifications in either location.
-```powershell
-.\rclone.exe bisync "$locationA" "$locationB" --create-empty-src-dirs --compare size,modtime,checksum --resilient --log-level ERROR --drive-skip-gdocs --fix-case --resync
-```
+=== "Initial Sync"
+    You only run this command the first time you sync the local and remote locations.  It builds a database between the two locations to effectively "index" every file locally and remotely, so that subsequent syncs can track deletions, additions, and modifications in either location.
 
-**Subsequent Syncs**:
-You run this command after the initial sync to check for changes, and push those changes to both locations.  For example, if a 
-```powershell
-.\rclone.exe bisync "$locationA" "$locationB" --create-empty-src-dirs --compare size,modtime,checksum --resilient --log-level ERROR --drive-skip-gdocs --fix-case --force
-```
+    ```powershell
+    .\rclone.exe bisync "$locationA" "$locationB" --create-empty-src-dirs --compare size,modtime,checksum --resilient --log-level ERROR --drive-skip-gdocs --fix-case --resync
+    ```
+        
+=== "Subsequent Syncs"
+    You run this command after the initial sync to check for changes, and push those changes to both locations. 
+    ```powershell
+    .\rclone.exe bisync "$locationA" "$locationB" --create-empty-src-dirs --compare size,modtime,checksum --resilient --log-level ERROR --drive-skip-gdocs --fix-case --force
+    ```
 
 ??? example "Self-Testing Powershell Script"
     You may not be 100% confident in the behavior of rclone, especially with something such as the `bisync` command in rclone.  If that is the case, you can run (and modify to your liking) the following powershell script to validate it behaves as you expect it would.