style: typo, styling

SignalK · Feb 28, 2018 · 4ce828d · 4ce828d
1 parent 9e1b45d
commit 4ce828d
Show file tree

Hide file tree

Showing 2 changed files with 98 additions and 114 deletions.
diff --git a/SECURITY.md b/SECURITY.md
@@ -16,11 +16,11 @@ ACLs
 
 Access control lists allow fine grained control of access to specific data in SignalK. The acls are a list which allow specifiying controls for specifc contexts and it goes in the security.json file mentioned above.
 
-The following example defines acls for the self context. It allows anyone to read the paths "steering.*", "navigation.*", "name", "design.aisShipType" and allows the admin user permission to write (update) those paths. 
+The following example defines acls for the self context. It allows anyone to read the paths `"steering.*"`, `"navigation.*"`, `"name"`, `"design.aisShipType"` and allows the admin user permission to write (update) those paths. 
 
-The second entry allows the user john to read any data coming from the 'actisense.35' $source.
+The second entry allows the user _john_ to read any data coming from the `actisense.35` $source.
 
-The in the last entrey, for all other paths, only the admin user can read and no one can write. 
+The last entry covers all other paths, allowing only the admin user to read and no one can write.
 
 If there is no match is found for a specific path in the acl list, then permission will be denied to that path.