Update pihole.toml documentation

[pralor-bot]

Automated PR to update pihole.toml documentation from FTL build.

[netlify]

✅ Deploy Preview for pihole-docs ready!

Name	Link
🔨 Latest commit	7fc9444
🔍 Latest deploy log	https://app.netlify.com/projects/pihole-docs/deploys/686923240d89e500084f0518
😎 Deploy Preview	https://deploy-preview-1258--pihole-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[rdwebdesign]

@PromoFaux

One of the linting rules is wrongly identifying 2 asterisks as italic markers.

Since these asterisks are normal text (not used to format the text as Italic), they contain spaces around them and this is triggering the MD037 rule:

This is the text. The highlighted part is not in italic, but the linter is throwing an error:

format, and it must have both, private key and certificate (the *.pem file created must contain a 'CERTIFICATE' section as well as a 'RSA PRIVATE KEY' section). The *.pem file can be created using cp server.crt server.pem

The same happens here, between the 2 _esni (lines 69 and 78).

Maybe we need to escape asterisks and underscores, or just disable rule MD037 for the file.

[PromoFaux]

Already identified and fixed - see latest commit :)

[rdwebdesign]

This is not a big issue, but why is privacylevel not using table format?

EDIT:

I think I found the reason.

Apparently the only difference between this "Possible values" section and the other sections is: The values here are not strings (the values are not inside quotes):

• privacylevel is configured as integer (no quotes):

  

• other options are configured as strings (quotes):

  

[rdwebdesign]

I also noticed the AI removed the code for escape angled brackets, resulting in missing text:

This:

  # Possible values are:
  #     <any valid domain>

Was printed just as:

Possible values are:

The text between < and > were considered a HTML tag an not printed.