summaryrefslogtreecommitdiff
path: root/docs/configuration/policy
diff options
context:
space:
mode:
authorYuriy Andamasov <yuriy@vyos.io>2026-05-05 23:21:35 +0300
committerYuriy Andamasov <yuriy@vyos.io>2026-05-06 16:18:03 +0300
commitd72e213cc7c2dd0099f305cda4a6ba527b27d1da (patch)
tree783b5f504e1a8d367148f2c140a403dc35cb6868 /docs/configuration/policy
parent80c5ca4aebb666932f681d2be0e7712e22d97f47 (diff)
downloadvyos-documentation-d72e213cc7c2dd0099f305cda4a6ba527b27d1da.tar.gz
vyos-documentation-d72e213cc7c2dd0099f305cda4a6ba527b27d1da.zip
docs: fix typos and a few grammar issues (ported from #1852 RST → MyST)
Ports the typo/grammar sweep originally captured in PR #1852 from .rst files to their .md equivalents, plus the eventhandler grammar fix that Copilot flagged in #1852's review (which the RST PR explicitly skipped as scope-stretch). Sources: - 73 typo/grammar substitutions from PR #1852 (rebased from #1801) - "Using environments is more preferable" → "Using environment variables is preferable" (Copilot review comment on #1852) #1852 itself is being discarded since it targets RST and we are phasing out the RST tree in favor of MyST. The 4 RST-linter line-wrap comments and 1 RST section-underline comment from Copilot's #1852 review are RST-specific and do not apply to .md. 🤖 Generated by [robots](https://vyos.io)
Diffstat (limited to 'docs/configuration/policy')
-rw-r--r--docs/configuration/policy/md-examples.md4
-rw-r--r--docs/configuration/policy/md-route-map.md2
-rw-r--r--docs/configuration/policy/md-route.md6
3 files changed, 6 insertions, 6 deletions
diff --git a/docs/configuration/policy/md-examples.md b/docs/configuration/policy/md-examples.md
index 2b5d54d2..4dc3f3b0 100644
--- a/docs/configuration/policy/md-examples.md
+++ b/docs/configuration/policy/md-examples.md
@@ -152,8 +152,8 @@ ISP's and VyOS router will respond from the same interface that the packet was
received. Also, it used, if we want that one VPN tunnel to be through one
provider, and the second through another.
-- `203.0.113.254` IP addreess on VyOS eth1 from ISP1
-- `192.168.2.254` IP addreess on VyOS eth2 from ISP2
+- `203.0.113.254` IP address on VyOS eth1 from ISP1
+- `192.168.2.254` IP address on VyOS eth2 from ISP2
- `table 10` Routing table used for ISP1
- `table 11` Routing table used for ISP2
diff --git a/docs/configuration/policy/md-route-map.md b/docs/configuration/policy/md-route-map.md
index 624b542c..cf419a48 100644
--- a/docs/configuration/policy/md-route-map.md
+++ b/docs/configuration/policy/md-route-map.md
@@ -1,6 +1,6 @@
# Route Map Policy
-Route map is a powerfull command, that gives network administrators a very
+Route map is a powerful command, that gives network administrators a very
useful and flexible tool for traffic manipulation.
## Configuration
diff --git a/docs/configuration/policy/md-route.md b/docs/configuration/policy/md-route.md
index 828bd0f1..b3ef6540 100644
--- a/docs/configuration/policy/md-route.md
+++ b/docs/configuration/policy/md-route.md
@@ -211,7 +211,7 @@ Set IPSec inbound match criterias, where:
```{cfgcmd} set policy route6 \<name\> rule \<n\> limit burst \<0-4294967295\>
-Set maximum number of packets to alow in excess of rate.
+Set maximum number of packets to allow in excess of rate.
```
```{cfgcmd} set policy route \<name\> rule \<n\> limit rate \<text\>
@@ -351,8 +351,8 @@ Match hop-limit parameter, where 'eq' stands for 'equal'; 'gt' stands for
### Actions
-When mathcing all patterns defined in a rule, then different actions can
-be made. This includes droping the packet, modifying certain data, or
+When matching all patterns defined in a rule, then different actions can
+be made. This includes dropping the packet, modifying certain data, or
setting a different routing table.
```{cfgcmd} set policy route \<name\> rule \<n\> action drop