Merge pull request #1316 from 0xflotus/patch-1

chore: fix errors in docs

.changelog/6fa199b732dc40c58481d369ce992eb3.md

@@ -0,0 +1,4 @@
+---
+type: none
+---
+Spelling/type-o corrections in docs

docs/dynamic_records.rst

@@ -59,14 +59,14 @@ An Annotated Example
       - geos:
         # AF-ZA was sent to apac above and the rest of AF else goes to eu here,
         # sub-locations (e.g. AF-ZA) should come before their parents (AF.) If a
-        # more specific geo occured after a general one requests in that
+        # more specific geo occurred after a general one requests in that
         # location would have already matched the previous rule. For the same
         # reasons locations may not be repeated in multiple rules.
         - AF
         - EU
         pool: eu
       # No geos means match all queries, the final rule should generally be a
-      # "catch-all", served to any requests that didn't match the preceeding
+      # "catch-all", served to any requests that didn't match the preceding
       # rules. The catch-all is the only case where a pool may be re-used.
       - pool: na
     ttl: 60
@@ -75,7 +75,7 @@ An Annotated Example
     # should be a superset of the catch-all pool and include enough capacity to
     # try and serve all global requests (with degraded performance.) The main
     # case they will come into play is if all dynamic healthchecks are failing,
-    # either on the service side or if the providers systems are expeiencing
+    # either on the service side or if the providers systems are experiencing
     # problems. They will also be used for when the record is pushed to a
     # provider that doesn't support dynamic records.
     values:

docs/dynamic_zone_config.rst

@@ -69,13 +69,13 @@ The following octoDNS configuration would match them as described in comments::
   zones:
 
     # the names here do not really matter beyond starting with a *, it is a
-    # reccomended best practice to match the glob, but not required. It will be
+    # recommended best practice to match the glob, but not required. It will be
     # used in logging to aid in debugging.
 
     # they are applied in the order defined and once claimed a zone is no
     # longer available for matching
 
-    # everytyhing is available for matching
+    # everything is available for matching
     '*internal.net':
       # we only want the private zones here and they are all under
       # internet.net. so this glob will claim them.
@@ -142,7 +142,7 @@ The following octoDNS configuration would match them as described in comments::
     # regexes are too ugly to use as names, so these have useful info for
     # logging/debugging
 
-    # everytyhing is available for matching
+    # everything is available for matching
     '*us-east-1':
       # we only want the private zones here and they are all under
       # internet.net. So this regex will claim them, yes this could be done
@@ -154,7 +154,7 @@ The following octoDNS configuration would match them as described in comments::
         # only push it to the us-east-1 provider
         - us-east-1
 
-    # everytyhing with the exception of the us-east-1 .net zones are available
+    # everything with the exception of the us-east-1 .net zones are available
     '*us-west-2':
       regex: '^.*us-west-2.*.net.$'
       sources: