From: Christoph Heiss <c.heiss@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] [PATCH datacenter-manager] docs: roadmap, sdn-integration: fix typos
Date: Fri, 5 Dec 2025 12:24:59 +0100 [thread overview]
Message-ID: <20251205112501.371141-1-c.heiss@proxmox.com> (raw)
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
docs/roadmap.rst | 2 +-
docs/sdn-integration.rst | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/roadmap.rst b/docs/roadmap.rst
index 1b17bbc..2743950 100644
--- a/docs/roadmap.rst
+++ b/docs/roadmap.rst
@@ -40,7 +40,7 @@ Roadmap
- Allow to add the pre-defined Updates, Firewall or Task tabs from the Remotes panel.
- Allow to create tabs to organize complex views.
- Evaluate other layouting options for rendering the card widgets.
- - Extending the filter capabillity by providing more types and evaluate more flexible comparission
+ - Extending the filter capability by providing more types and evaluate more flexible comparisons
operators.
diff --git a/docs/sdn-integration.rst b/docs/sdn-integration.rst
index 1192830..83381a8 100644
--- a/docs/sdn-integration.rst
+++ b/docs/sdn-integration.rst
@@ -32,11 +32,11 @@ instances of all configured clusters.
The EVPN integration respects the ‘Route Target Import’ field of an EVPN zone and assumes any Zones
/ Vnets with that Route Target are imported as well.
-Defintions
+Definitions
^^^^^^^^^^
Currently, the SDN stack in Proxmox VE uses the terms Zones and VNets, which are specific to the
-Proxmox VE stack. The following defintions try to make the relationship of those entities to the
+Proxmox VE stack. The following definitions try to make the relationship of those entities to the
more commonly used definitions in RFC 7432 and RFC 9136 clearer:
A EVPN zone represents a routing table instance (identified by its ASN:VNI tag). This is also known
--
2.51.2
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next reply other threads:[~2025-12-05 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 11:24 Christoph Heiss [this message]
2025-12-05 11:43 ` [pdm-devel] applied: " Thomas Lamprecht
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=20251205112501.371141-1-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pdm-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