docs(advanced): fix markdown formatting in split-horizon guide

Co-Authored-By: Claude <[email protected]>

Author: lexfrei

charts/external-dns/values.schema.json

@@ -13,6 +13,13 @@
         "null"
       ]
     },
+    "annotationPrefix": {
+      "description": "Annotation prefix for external-dns annotations (useful for split horizon DNS with multiple instances).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
     "automountServiceAccountToken": {
       "description": "Set this to `false` to [opt out of API credential automounting](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#opt-out-of-api-credential-automounting) for the `Pod`.",
       "type": "boolean"

docs/faq.md

@@ -274,6 +274,7 @@ This means that only those resources which match the selector specified in `--la
 For more advanced split horizon scenarios, you can use the `--annotation-prefix` flag to configure different instances to read different sets of annotations from the same resources. This is useful when you want a single Service or Ingress to create records in multiple DNS zones (e.g., internal and external).
 
 For example:
+
 ```bash
 # Internal DNS instance
 --annotation-prefix=internal.company.io/ --provider=aws --aws-zone-type=private
@@ -283,6 +284,7 @@ For example:
 ```
 
 Then annotate your resources with both prefixes:
+
 ```yaml
 metadata:
   annotations: