update

caddy_v2/readme.md

@@ -390,13 +390,15 @@ network be allowed through?<br>
 Well, the [remote_ip](https://caddyserver.com/docs/caddyfile/matchers#remote-ip)
 matcher comes to play, which enables you to filter requests by their IP.<br>
 
-* *note* - if your router uses hairpin/NATreflection to get around
+* *note:* if your router uses hairpin/NATreflection to get around
   [the issue](https://github.com/DoTheEvo/selfhosted-apps-docker/tree/master/caddy_v2#editing-hosts-file)
   of accessing locally hosted stuff from LAN side by the hostname,
   then this will block LAN side too. As remote_ip will be your public ip.
   Local DNS server is needed, with records sending traffic to docker host
   instead of hairpin/NATreflection
 
+* *note:* a shortuc `private_ranges` can be used, instead of specific range
+
 Named matchers are defined by `@` and can be named whatever you like.
 
 ```
@@ -426,7 +428,7 @@ Requests matching that rule get the response 403 - forbidden.
 What if you need to have the same matcher in several site-blocks and
 would prefer for config to look cleaner? 
 
-Here comes the [snippets](https://caddyserver.com/docs/caddyfile/concepts#snippets).<br>
+Here come [snippets](https://caddyserver.com/docs/caddyfile/concepts#snippets).<br>
 Snippets are defined under the global options block,
 using parentheses, named whatever you like.<br>
 They then can be used inside any site-block with simple `import <snippet name>`
@@ -554,7 +556,7 @@ The drawback is a potential security issue, since you are creating a token
 that allows full control over your domain's DNS. You store this token somewhere,
 you are giving it to some application from dockerhub...
 
-*note*: caddy uses a new [libdns](https://github.com/libdns/libdns/)
+*note:* caddy uses a new [libdns](https://github.com/libdns/libdns/)
 golang library with [cloudflare package](https://github.com/libdns/cloudflare)
 
 ### - Create API token on Cloudflare