diff options
author | 2016-08-22 14:40:24 -0700 | |
---|---|---|
committer | 2016-08-22 14:40:24 -0700 | |
commit | 938ecbeab994db40d41f3b310218a5cd10d01184 (patch) | |
tree | aecd1f49771969781eda2d9c505f54130de8666c | |
parent | 9a3fa013d6fa6befdeff4e4e15b9a97c0daadde4 (diff) | |
download | coredns-938ecbeab994db40d41f3b310218a5cd10d01184.tar.gz coredns-938ecbeab994db40d41f3b310218a5cd10d01184.tar.zst coredns-938ecbeab994db40d41f3b310218a5cd10d01184.zip |
Update README.md
Grammatical fixes.
-rw-r--r-- | middleware/secondary/README.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/middleware/secondary/README.md b/middleware/secondary/README.md index c2b1366e7..6ef8ebc3b 100644 --- a/middleware/secondary/README.md +++ b/middleware/secondary/README.md @@ -9,7 +9,7 @@ secondary [zones...] ~~~ * `zones` zones it should be authoritative for. If empty, the zones from the configuration block - are used. Not that with an remote address to *get* the zone the above is not that useful. + are used. Note that without a remote address to *get* the zone from, the above is not that useful. A working syntax would be: @@ -20,9 +20,9 @@ secondary [zones...] { } ~~~ -* `transfer from` tell from which address to fetch the zone. It can be specified multiple time, - if one does not work another will be tried. -* `transfer to` can be enabled to allow this secondary zone to be transfered again. +* `transfer from` specifies from which address to fetch the zone. It can be specified multiple times; + if one does not work, another will be tried. +* `transfer to` can be enabled to allow this secondary zone to be transferred again. ## Examples |