From 5a8da8296c59a233cececf858fa1ee27a08e12c8 Mon Sep 17 00:00:00 2001 From: 0xflotus <0xflotus@gmail.com> Date: Thu, 16 Oct 2025 00:10:05 +0200 Subject: [PATCH] chore: fix typos in dynamic_zone_config.rst --- docs/dynamic_zone_config.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/dynamic_zone_config.rst b/docs/dynamic_zone_config.rst index c6cd36b..78adf31 100644 --- a/docs/dynamic_zone_config.rst +++ b/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: