[WIP] Add spellchecker

.gitignore

@@ -0,0 +1,2 @@
+.DS_Store
+admin_guide/.DS_Store

.travis.yml

@@ -0,0 +1,6 @@
+services:
+- docker
+
+script:
+- make
+

Makefile

@@ -0,0 +1,8 @@
+
+RESULT := $(shell (docker run --rm -v "$(PWD):/workdir" tmaier/hunspell -u3 -d en_US -p our_dict admin_guide/access_control/*.adoc))
+
+test:
+	@echo "$(RESULT)"
+	@if [ "$(RESULT)" != "" ]; then\
+        exit 1;\
+	fi

admin_guide/access_control/access_control.adoc

@@ -6,5 +6,5 @@ Prisma Cloud provides broad enterprise identity support, integrating with Active
 Define accounts and IAM roles to integrate with your cloud providers in one place and reuse them across the product.
 Pluggable cryptography allows you to bring your own certificates, not just for TLS, but also for smart card authentication to Console.
 
-Prisma Cloud ships with prebuilt roles to provide least privilege access to your devops and security teams.
+Prisma Cloud ships with prebuilt roles to provide least privilege access to your DevOps and security teams.
 Use Assigned Collections to precisely control what data teams can view or use built-in multi-tenancy to securely isolate entire business units or geographies within the same Console.

admin_guide/access_control/access_keys.adoc

@@ -87,7 +87,7 @@ This role will be assigned to your service account.
 
 . (Optional) Allow your service account to authenticate directly with Prisma Cloud.
 +
-If you've integrated Prisma Cloud with a directory service, creating a new user in your underlying auth provider can be tedious in some enterprise environments.
+If you have integrated Prisma Cloud with a directory service, creating a new user in your underlying auth provider can be tedious in some enterprise environments.
 Prisma Cloud lets select users authenticate directly with Prisma Cloud using their email and a password that's registered separately after the user account is created.
 
 .. In Prisma Cloud, go to *Settings > SSO*.

admin_guide/access_control/integrate_saml.adoc

@@ -76,7 +76,7 @@ image::integrate_saml_610136.png[width=600]
 
 .. In the *Single Sign On URL* field, enter *\https://<CONSOLE_ADDR>:8083/api/v1/authenticate*.
 +
-Note that if you've changed the default port you use for the HTTPS listener, you'd need to adjust the URL here accordingly.
+Note that if you have changed the default port you use for the HTTPS listener, you'd need to adjust the URL here accordingly.
 Additionally, this URL must be visible from the Okta environment, so if you're in a virtual network or behind a load balancer, it must be configured to forward traffic to this port and it's address is what should be used here.
 
 .. Select *Use this for Recipient URL and Destination URL*.

admin_guide/access_control/open_policy_agent.adoc

@@ -87,7 +87,7 @@ For Kubernetes v1.16 or later, copy the v1.16 template from <<_templates,here>>.
 
 . Create the webhook configuration object.
 +
-After creating the object, the Kubenetest API server directs AdmissionReview requests to Defender.
+After creating the object, the Kubernetes API server directs AdmissionReview requests to Defender.
 
   $ kubectl apply -f webhook.yaml