summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Poessinger <christian@poessinger.com>2018-10-03 15:02:24 +0200
committerChristian Poessinger <christian@poessinger.com>2018-10-03 15:02:24 +0200
commit2022dd397eb6612f44d1e0c5b548b4ccaceb8a2c (patch)
tree34a19619a1ca306fc28bce4d7c5cb53e6ec47894
parent1417911523ab5095a69c067c8c861ff77e318b00 (diff)
downloadvyos-documentation-2022dd397eb6612f44d1e0c5b548b4ccaceb8a2c.tar.gz
vyos-documentation-2022dd397eb6612f44d1e0c5b548b4ccaceb8a2c.zip
Replace all occurances of 'Note:' with 'NOTE:'
-rw-r--r--docs/ch01-install.rst2
-rw-r--r--docs/ch08-nat.rst4
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/ch01-install.rst b/docs/ch01-install.rst
index 1c03e424..3b4da506 100644
--- a/docs/ch01-install.rst
+++ b/docs/ch01-install.rst
@@ -28,7 +28,7 @@ version if something breaks after upgrade. Every version is contained in its
own squashfs image that is mounted in a union filesystem together with a
directory for mutable data (configs etc.).
-**Note:** older versions used to support non-image installation (`install
+**NOTE:** older versions used to support non-image installation (`install
system` command). It's been deprecated since the time image installation was
introduced (long before the fork), and does not provide any version management
capabilities. You **should not** use it for new installations even if it's still
diff --git a/docs/ch08-nat.rst b/docs/ch08-nat.rst
index 8d930356..9b7f9c34 100644
--- a/docs/ch08-nat.rst
+++ b/docs/ch08-nat.rst
@@ -57,7 +57,7 @@ rule [n] translation address` statement.
set nat source rule 100 translation address '203.0.113.32-203.0.113.63'
-**Note:** Avoiding "leaky" NAT
+**NOTE:** Avoiding "leaky" NAT
Linux netfilter will not NAT traffic marked as INVALID. This often confuses
people into thinking that Linux (or specifically VyOS) has a broken NAT
@@ -82,7 +82,7 @@ protocol behavior. For this reason, VyOS does not globally drop invalid state
traffic, instead allowing the operator to make the determination on how the
traffic is handled.
-**Note:** Avoiding NAT breakage in the absence of split-DNS
+**NOTE:** Avoiding NAT breakage in the absence of split-DNS
A typical problem with using NAT and hosting public servers is the ability for
internal systems to reach an internal server using it's external IP address.