[pdm-devel] [PATCH datacenter-manager] docs: roadmap, sdn-integration: fix typos

[Christoph Heiss]

Signed-off-by: Christoph Heiss <c.heiss at 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