From 5ea22c0f6d608aa80ec5d361283f0c9e81b71441 Mon Sep 17 00:00:00 2001
From: Ming Di Leom <2809763-curben@users.noreply.gitlab.com>
Date: Sat, 24 Feb 2024 09:43:26 +0000
Subject: [PATCH] post(splunk-app-acl): read vs write access

---
 source/_posts/splunk-app-acl.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_posts/splunk-app-acl.md b/source/_posts/splunk-app-acl.md
index 5020a6c..14ec77c 100644
--- a/source/_posts/splunk-app-acl.md
+++ b/source/_posts/splunk-app-acl.md
@@ -38,7 +38,7 @@ None of the above configs will grant roleB read access to lookupB.csv. For the r
 - If any layer does not permit read access, the object will not be accessible.
 ```
 
-> For brevity, this article will only discuss about read access which has slightly different interaction of ACLs. Don't worry, once you understood read access, it's much easier to understand write access.
+> For brevity, this article will only discuss about read access which has slightly different interaction of ACLs compared to write access. Don't worry, once you understood read access, it's much easier to understand write access.
 
 Notice a role must at least have read access to the app. The simplest way to grant roleB read access is,