From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] docs: fix typos
Date: Mon, 22 Dec 2025 10:57:24 +0100 [thread overview]
Message-ID: <20251222095736.259415-1-m.sandoval@proxmox.com> (raw)
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
kernel-samepage-merging.adoc | 2 +-
pve-storage-lvm.adoc | 2 +-
vxlan-and-evpn.adoc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel-samepage-merging.adoc b/kernel-samepage-merging.adoc
index e2e70d72..5289d714 100644
--- a/kernel-samepage-merging.adoc
+++ b/kernel-samepage-merging.adoc
@@ -36,7 +36,7 @@ Disabling KSM
KSM can be disabled on a node or on a per-VM basis.
-.Disabe KSM on a Node
+.Disable KSM on a Node
To see if KSM is active on a node, you can check the output of:
diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc
index b81bf976..351749b7 100644
--- a/pve-storage-lvm.adoc
+++ b/pve-storage-lvm.adoc
@@ -49,7 +49,7 @@ to zero blocks. Otherwise, a fallback to `cstream` is performed.
`saferemove-stepsize`::
-Wipe step size in MiB (`blkdiscard -p` paramater value), capped to the maximum
+Wipe step size in MiB (`blkdiscard -p` parameter value), capped to the maximum
step size supported by the underlying storage. Up to 32 MiB (maximum) by
default.
diff --git a/vxlan-and-evpn.adoc b/vxlan-and-evpn.adoc
index 12bcea90..3f9c14bc 100644
--- a/vxlan-and-evpn.adoc
+++ b/vxlan-and-evpn.adoc
@@ -794,7 +794,7 @@ symmetric model
With this model, you don't need to have all vxlan on all nodes.
This model will also be needed to route traffic to an external router.
-The symmetric model routes and bridges on both the ingress and the egress leafs.
+The symmetric model routes and bridges on both the ingress and the egress leaves.
This results in bi-directional traffic being able to travel on the same VNI, hence the symmetric name.
However, a new specialty transit VNI is used for all routed VXLAN traffic, called the L3VNI.
All traffic that needs to be routed will be routed onto the L3VNI, tunneled across the layer 3 Infrastructure,
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-12-22 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 9:57 Maximiliano Sandoval [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-17 13:03 Maximiliano Sandoval
2024-07-22 13:58 ` Aaron Lauterer
2024-07-25 8:29 ` Maximiliano Sandoval
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251222095736.259415-1-m.sandoval@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.