From c80f8a606be48cbc0ac809e815eb942575e9f284 Mon Sep 17 00:00:00 2001 From: Jeffrey Cafferata Date: Sat, 11 Mar 2023 14:53:37 +0100 Subject: [PATCH] DOCS: Fixed the incorrect inline anchors links (#2132) Co-authored-by: Tom Limoncelli --- documentation/opinions.md | 4 ++-- documentation/writing-providers.md | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/documentation/opinions.md b/documentation/opinions.md index becc235d5..71256a2ef 100644 --- a/documentation/opinions.md +++ b/documentation/opinions.md @@ -73,7 +73,7 @@ the DNS names are downcased. This reduces code complexity, reduces the number of edge-cases that must be tested, and makes the system safer to operate. -Yes, we know that DNS is case insensitive. See [Opinion #3](#opinion-3--dnsconfigjs-are-not-zonefiles). +Yes, we know that DNS is case insensitive. See [Opinion #3](#opinion-3-dnsconfig.js-are-not-zonefiles). # Opinion #5: Users should state what they want, and DNSControl should do the rest @@ -93,7 +93,7 @@ Some examples: # Opinion #6 If it is ambiguous in DNS, it is forbidden in DNSControl When there is ambiguity an expert knows what the system will do. -Your coworkers should not be expected to be experts. (See [Opinion #2](#opinion-2--non-experts-should-be-able-to-safely-make-dns-changes)). +Your coworkers should not be expected to be experts. (See [Opinion #2](#opinion-2-non-experts-should-be-able-to-safely-make-dns-changes)). We would rather DNSControl error out than require users to be DNS experts. diff --git a/documentation/writing-providers.md b/documentation/writing-providers.md index daf9148cf..50ed5a7ec 100644 --- a/documentation/writing-providers.md +++ b/documentation/writing-providers.md @@ -281,9 +281,9 @@ dependencies. Here are some last-minute things to check before you submit your PR. 1. Run `go generate` to make sure all generated files are fresh. -2. Make sure all appropriate documentation is current. (See [Step 8](#step-8--manual-tests)) -3. Check that dependencies are current (See [Step 13](#step-13--dependencies)) -4. Re-run the integration test one last time (See [Step 7](#step-7--integration-test)) +2. Make sure all appropriate documentation is current. (See [Step 8](#step-8-manual-tests)) +3. Check that dependencies are current (See [Step 13](#step-13-dependencies)) +4. Re-run the integration test one last time (See [Step 7](#step-7-integration-test)) ## Step 15: After the PR is merged