diff options
| -rw-r--r-- | docs/automation/terraform/terraformAWS.md | 2 | ||||
| -rw-r--r-- | docs/configuration/nat/nat44.md | 4 | ||||
| -rw-r--r-- | docs/configuration/policy/route.md | 4 | ||||
| -rw-r--r-- | docs/configuration/protocols/bgp.md | 6 | ||||
| -rw-r--r-- | docs/configuration/protocols/ospf.md | 2 | ||||
| -rw-r--r-- | docs/configuration/protocols/traffic-engineering.md | 2 | ||||
| -rw-r--r-- | docs/configuration/service/console-server.md | 2 | ||||
| -rw-r--r-- | docs/configuration/service/router-advert.md | 2 | ||||
| -rw-r--r-- | docs/configuration/service/webproxy.md | 2 | ||||
| -rw-r--r-- | docs/configuration/system/conntrack.md | 2 | ||||
| -rw-r--r-- | docs/contributing/debugging.md | 2 | ||||
| -rw-r--r-- | docs/vpp/configuration/ipsec.md | 2 |
12 files changed, 16 insertions, 16 deletions
diff --git a/docs/automation/terraform/terraformAWS.md b/docs/automation/terraform/terraformAWS.md index 488e7926..d4e38d46 100644 --- a/docs/automation/terraform/terraformAWS.md +++ b/docs/automation/terraform/terraformAWS.md @@ -305,7 +305,7 @@ Make sure Ansible can ping from Terraform. ├── vyos.tf # The main script ├── var.tf # The file of all variables in "vyos.tf" ├── versions.tf # File for the changing version of Terraform. -└── terraform.tfvars # The value of all variables (passwords, login, ip adresses and so on) +└── terraform.tfvars # The value of all variables (passwords, login, ip addresses and so on) ``` ## File contents of Terraform for AWS diff --git a/docs/configuration/nat/nat44.md b/docs/configuration/nat/nat44.md index 8b02477e..2e877106 100644 --- a/docs/configuration/nat/nat44.md +++ b/docs/configuration/nat/nat44.md @@ -298,8 +298,8 @@ randomly. When defining the translated address, called `backends`, a `weight` must be configured. This lets the user define load balance distribution according -to their needs. Them sum of all the weights defined for the backends should -be equal to 100. In oder words, the weight defined for the backend is the +to their needs. The sum of all the weights defined for the backends should +be equal to 100. In other words, the weight defined for the backend is the percentage of the connections that will receive such backend. ```{cfgcmd} set nat [source | destination] rule \<rule\> load-balance hash [source-address | destination-address | source-port | destination-port | random] diff --git a/docs/configuration/policy/route.md b/docs/configuration/policy/route.md index b3ef6540..d2a6e8fa 100644 --- a/docs/configuration/policy/route.md +++ b/docs/configuration/policy/route.md @@ -201,7 +201,7 @@ about what type-name criteria are supported. ```{cfgcmd} set policy route6 \<name\> rule \<n\> ipsec \<match-ipsec|match-none\> -Set IPSec inbound match criterias, where: +Set IPSec inbound match criteria, where: * match-ipsec: match inbound IPsec packets. * match-none: match inbound non-IPsec packets. ``` @@ -270,7 +270,7 @@ Match based on packet type criteria. ```{cfgcmd} set policy route6 \<name\> rule \<n\> recent time \<1-4294967295\> Set parameters for matching recently seen sources. This match could be used -by seeting count (source address seen more than <1-255> times) and/or time +by setting count (source address seen more than <1-255> times) and/or time (source address seen in the last <0-4294967295> seconds). ``` diff --git a/docs/configuration/protocols/bgp.md b/docs/configuration/protocols/bgp.md index 702a2b1f..ff0d24e2 100644 --- a/docs/configuration/protocols/bgp.md +++ b/docs/configuration/protocols/bgp.md @@ -285,7 +285,7 @@ and happen automatically if local-role is set. ```{cfgcmd} set protocols bgp neighbor \<address|interface\> shutdown -This command disable the peer or peer group. To reenable the peer use +This command disable the peer or peer group. To re-enable the peer use the delete form of this command. ``` @@ -805,7 +805,7 @@ availability is also advertised. A route that continually fails and returns requires a great deal of network traffic to update the network about the route's status. -Route dampening wich described in {rfc}`2439` enables you to identify routes +Route dampening which described in {rfc}`2439` enables you to identify routes that repeatedly fail and return. If route dampening is enabled, an unstable route accumulates penalties each time the route fails and returns. If the accumulated penalties exceed a threshold, the route is no longer advertised. @@ -1016,7 +1016,7 @@ peer. The {cfgcmd}`receive` keyword configures a router to advertise ORF receive capabilities. The {cfgcmd}`send` keyword configures a router to advertise ORF send capabilities. To advertise a filter from a sender, you must create an IP prefix list for the specified BGP peer applied in inbound -derection. +direction. ``` diff --git a/docs/configuration/protocols/ospf.md b/docs/configuration/protocols/ospf.md index 72fefb84..3e721441 100644 --- a/docs/configuration/protocols/ospf.md +++ b/docs/configuration/protocols/ospf.md @@ -1403,7 +1403,7 @@ This command displays the neighbor DR choice information. ```{opcmd} show ipv6 ospfv3 interface [prefix]|[\<interface\> [prefix]] This command displays state and configuration of OSPF the specified -interface, or all interfaces if no interface is given. Whith the argument +interface, or all interfaces if no interface is given. With the argument {cfgcmd}`prefix` this command shows connected prefixes to advertise. ``` ```{opcmd} show ipv6 ospfv3 route diff --git a/docs/configuration/protocols/traffic-engineering.md b/docs/configuration/protocols/traffic-engineering.md index 832023a7..27d54af8 100644 --- a/docs/configuration/protocols/traffic-engineering.md +++ b/docs/configuration/protocols/traffic-engineering.md @@ -11,7 +11,7 @@ Traffic Engineering parameters are used for both IS-IS and OSPF (not supported y ```{cfgcmd} set protocols traffic-engineering admin-group \<admin-group-name\> bit-position \<bit-position-value\> -Create Administrative group and assosiate bit position with it. These groups can be +Create Administrative group and associate bit position with it. These groups can be used in the following commands. \<bit-position-value\> can have value 0-31. There cannot be two groups with same bit position. diff --git a/docs/configuration/service/console-server.md b/docs/configuration/service/console-server.md index f0556652..87464c88 100644 --- a/docs/configuration/service/console-server.md +++ b/docs/configuration/service/console-server.md @@ -60,7 +60,7 @@ left unconfigured. :::{note} USB to serial converters will handle most of their work in software -so you should be carefull with the selected baudrate as some times they +so you should be careful with the selected baudrate as some times they can't cope with the expected speed. ::: ``` diff --git a/docs/configuration/service/router-advert.md b/docs/configuration/service/router-advert.md index 10753105..b81dddc7 100644 --- a/docs/configuration/service/router-advert.md +++ b/docs/configuration/service/router-advert.md @@ -108,7 +108,7 @@ Router Advertisements unless this option is set. ## Example Your LAN connected on eth0 uses prefix `2001:db8:beef:2::/64` with the router -beeing `2001:db8:beef:2::1` +being `2001:db8:beef:2::1` ```none set interfaces ethernet eth0 address 2001:db8:beef:2::1/64 diff --git a/docs/configuration/service/webproxy.md b/docs/configuration/service/webproxy.md index 28156b2b..df675916 100644 --- a/docs/configuration/service/webproxy.md +++ b/docs/configuration/service/webproxy.md @@ -317,7 +317,7 @@ Defaults to 'uid' :::{note} This can only be done if all your users are located directly under the same position in the LDAP tree and the login name is used for naming -each user object. If your LDAP tree does not match these criterias or if you +each user object. If your LDAP tree does not match these criteria or if you want to filter who are valid users then you need to use a search filter to search for your users DN (filter-expression). ::: diff --git a/docs/configuration/system/conntrack.md b/docs/configuration/system/conntrack.md index 2b7279f6..e27e2187 100644 --- a/docs/configuration/system/conntrack.md +++ b/docs/configuration/system/conntrack.md @@ -175,7 +175,7 @@ the future the conntrack ignore rules will be removed. .. cfgcmd:: set system conntrack ignore [ipv4 | ipv6] rule <1-999999> tcp flags [not] <text> - Allowed values fpr TCP flags: ``ack``, ``cwr``, ``ecn``, ``fin``, ``psh``, + Allowed values for TCP flags: ``ack``, ``cwr``, ``ecn``, ``fin``, ``psh``, ``rst``, ``syn`` and ``urg``. Multiple values are supported, and for inverted selection use ``not``, as shown in the example. ``` diff --git a/docs/contributing/debugging.md b/docs/contributing/debugging.md index d3b4b513..f31fb8f3 100644 --- a/docs/contributing/debugging.md +++ b/docs/contributing/debugging.md @@ -193,7 +193,7 @@ You can also make this permanent by editing `/boot/grub/grub.cfg`. VyOS CLI depends heavily on priorities. Every CLI node has a corresponding `node.def` file and possibly an attached script. Nodes can have priorities, -and on system bootup or any `commit` to the configuration, scripts execute +and on system boot or any `commit` to the configuration, scripts execute from lowest to highest priority. This provides deterministic behavior. To debug priority issues or see script execution order, use the diff --git a/docs/vpp/configuration/ipsec.md b/docs/vpp/configuration/ipsec.md index 523b4a90..8d06f8f6 100644 --- a/docs/vpp/configuration/ipsec.md +++ b/docs/vpp/configuration/ipsec.md @@ -77,7 +77,7 @@ VPP **does not** support the following **integrity algorithms**: - AES CMAC - AES-GMAC -If you have configured ESP profiles with algorithms not supported by VPP and the traffic for such peers flows trough VPP interfaces, such traffic will be dropped. +If you have configured ESP profiles with algorithms not supported by VPP and the traffic for such peers flows through VPP interfaces, such traffic will be dropped. ## Configuration Examples |