From 29005c3035255b2be3fd3091c5861f668e4a1037 Mon Sep 17 00:00:00 2001
From: 0xflotus <0xflotus@gmail.com>
Date: Thu, 16 Oct 2025 00:07:53 +0200
Subject: [PATCH] chore: fix errors in docs

---
 docs/dynamic_records.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/dynamic_records.rst b/docs/dynamic_records.rst
index ca85a2e..b4bb88f 100644
--- a/docs/dynamic_records.rst
+++ b/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: