From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/2] pvesdn: fix section overview typos
Date: Wed, 27 Aug 2025 11:58:42 +0200 [thread overview]
Message-ID: <20250827095845.374470-2-c.heiss@proxmox.com> (raw)
In-Reply-To: <20250827095845.374470-1-c.heiss@proxmox.com>
A double colon on the first entry and a doubled 'VNets' prefix later on
in the same list.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
pvesdn.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pvesdn.adoc b/pvesdn.adoc
index 8759691..41c22ea 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -138,13 +138,13 @@ Configuration Overview
Configuration is done at the web UI at datacenter level, separated into the
following sections:
-* SDN:: Here you get an overview of the current active SDN state, and you can
+* SDN: Here you get an overview of the current active SDN state, and you can
apply all pending changes to the whole cluster.
* xref:pvesdn_config_zone[Zones]: Create and manage the virtually separated
network zones
-* xref:pvesdn_config_vnet[VNets] VNets: Create virtual network bridges and
+* xref:pvesdn_config_vnet[VNets]: Create virtual network bridges and
manage subnets
The Options category allows adding and managing additional services to be used
--
2.50.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-08-27 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 9:58 [pve-devel] [PATCH docs 0/2] pvesdn: fix overview typos, link dhcp section Christoph Heiss
2025-08-27 9:58 ` Christoph Heiss [this message]
2025-08-27 9:58 ` [pve-devel] [PATCH docs 2/2] pvesdn: link dhcp section in section overview Christoph Heiss
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=20250827095845.374470-2-c.heiss@proxmox.com \
--to=c.heiss@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox