From af2b6d77114b7ba392830961dbe40c29e56b24d4 Mon Sep 17 00:00:00 2001
From: asdffdsa6131 <42986211+asdffdsa6131@users.noreply.github.com>
Date: Sun, 8 Sep 2019 11:57:17 -0400
Subject: [PATCH] Updated How to enable VSS for rclone (markdown)

---
 How-to-enable-VSS-for-rclone.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/How-to-enable-VSS-for-rclone.md b/How-to-enable-VSS-for-rclone.md
index 087072b..54b1da4 100644
--- a/How-to-enable-VSS-for-rclone.md
+++ b/How-to-enable-VSS-for-rclone.md
@@ -68,7 +68,7 @@ So I will give you 3 workarounds for clear code for exec.cmd.
 
 --- Create a new drive letter. This is what I do as this is the most reliable and least code needed.
 Create a new drive and use that for the mount point.
-Most Windows computer hard drives will not have free space to create a new drive. So shrink your c: drive by just 1GB and use that space to create new partition and name it the b: drive. Since the b: drive will only be used to mount the vss point, 1GB is plenty of space, in fact 1MB is enough space.
+Most computers will not have free space to create a new drive. So shrink your c: drive by just 1MB and use that space to create new partition and name it the b: drive. Since the b: drive will only be used to mount the vss point, 1MB is plenty of space.
 
     call setvar.cmd
     mklink /d b:\snapshot\ %shadow_device_1%\