From d7ace56180e5597b07b563d1171283ca96749862 Mon Sep 17 00:00:00 2001
From: jkaufman-mitre <135844572+jkaufman-mitre@users.noreply.github.com>
Date: Mon, 10 Jun 2024 09:48:52 -0400
Subject: [PATCH] Update baselines/Google Drive and Docs Minimum Viable Secure
 Configuration Baseline v0.2.md

Co-authored-by: Alden Hilton <106177711+adhilto@users.noreply.github.com>
---
 ...nd Docs Minimum Viable Secure Configuration Baseline v0.2.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/baselines/Google Drive and Docs Minimum Viable Secure Configuration Baseline v0.2.md b/baselines/Google Drive and Docs Minimum Viable Secure Configuration Baseline v0.2.md
index 19a2ec37..2a5b98b9 100644
--- a/baselines/Google Drive and Docs Minimum Viable Secure Configuration Baseline v0.2.md	
+++ b/baselines/Google Drive and Docs Minimum Viable Secure Configuration Baseline v0.2.md	
@@ -368,7 +368,7 @@ This section addresses Drive for Desktop, a feature that enables users to intera
 ### Policies
 
 #### GWS.DRIVEDOCS.6.1v0.2
-Google Drive for Desktop SHOULD only be enabled for authorized devices.
+Google Drive for Desktop SHOULD be enabled only for authorized devices.
 
 - _Rationale:_ Some users may attempt to use Drive for Desktop to connect unapproved devices (e.g., a personal computer), to the agency's Google Drive. Even if done without malicious intent, this represents a security risk as the agency has no ability audit or protect such computers.
 - _Last modified:_ June 7, 2024