Making Vale happy

docs/architecture/config_decomposition/index.md

@@ -33,11 +33,11 @@ In general, we use a meta-service called demarcation point, to identify the phys
 
 ![](../../assets/images/TNC23_diagrams-Service_stitching.drawio.png){ width='400' }
 
-A service is always delivered on a VLAN (that can be native VLAN in some particula cases, for example IPtrunk). The VLAN is called "Service Delivery Point".
+A service is always delivered on a VLAN - that can be native VLAN in some particular cases, for example IPtrunk. The VLAN is called "Service Delivery Point".
 
 ## Separation of data and configuration
 
-Configuration can be seen as the composition of some abstract data structure that represent the business logic, and a template that match the router's specific config dialect.
+Configuration can be seen as the composition of some abstract data structure that represent the business logic, and a template that match the router's specific configuration dialect.
 In the following example we are going to configure DNS servers on a Juniper and a Nokia router:
 
 DNS servers (abstract data):

docs/architecture/index.md

@@ -44,7 +44,7 @@ LibreNMS is a general purpose monitoring system in use at GÉANT to gather relev
 More detailed information about this integration is available in the [LibreNMS integration module](../admin_guide/oss_bss/librenms.md)
 ### Kentik (planned)
 
-Kentik is a Network Observability tool and it collects serveral information from our PE routers. For this reason it is not in scope for PHASE1.
+Kentik is a Network Observability tool and it collects several information from our PE routers. For this reason it is not in scope for PHASE1.
 
 ### Inventory Provider (planned)
 

vale/styles/Vocab/geant-jargon/accept.txt

 IP/MPLS
+IPAM
 MPLS
 MTTR
 configuration as code