More Architecure documentation

docs/architecture/components/index.md

 # Components of GAP
 
-As previously stated, GAP is a platform and not a monolitic piece of software. GAP interacts with different OSS/BSS systems already present in GÉANT and these are tightly part of it in a certain sense.
+As previously stated, GAP is a platform and not a monolithic piece of software. GAP interacts with different OSS/BSS systems already present in GÉANT and these are tightly part of it in a certain sense.
 
 From a high level point of view, GAP can be seen as the sum of these parts:
 
-- __A service database__ called CoreDB that contains the models of the service intances, called _subscriptions_. Subscriptions are abstract objects that represent functional configuration constructs: the attributes that characterize these objects are defined in the _domain models_.
+- __A service database__ called CoreDB that contains the models of the service instances, called _subscriptions_. Subscriptions are abstract objects that represent functional configuration constructs: the attributes that characterize these objects are defined in the _domain models_.
 
 - __An orchestration engine__ called Workflow Orchestrator that is capable of executing lists of steps called workflows.
 
 - __A web interface__ for operators, called Orchestrator GUI to intuitively launch and inspect workflows.
 
-- __An automation engine__, Ansible, capable of intracting with network devices to configure them or to gather operational information.
+- __An automation engine__, Ansible, capable of interacting with network devices to configure them or to gather operational information.
 
 - __A set of authoritative systems to manage resources__:
     - IP addresses and DNS names (Infoblox)

docs/architecture/config_decomposition/index.md

@@ -33,7 +33,7 @@ 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 particular 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
 

docs/index.md

@@ -14,7 +14,7 @@ GAP represents the vision of GÉANT in terms of Network Automation and Orchestra
 
 GAP is partially based on Open Source Software and partially internally developed and integrates with most of the tooling already in use in GÉANT.
 
-!!! Acknoledgements
+!!! Credits
 
     The OSS components that GAP uses are mainly:
 

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

+Linecard
+APIs
 IP/MPLS
 IPAM
 MPLS