added attribution

Author: petercrocker

.metadata.yml

@@ -9,6 +9,7 @@ experimental/azure:
     - base
   description: This schema extension introduces cloud support for Microsoft Azure.
   name: Azure
+  attribution: "[Rowan Coleman](https://www.linkedin.com/in/rowan-coleman-6a147156/)"
 experimental/circuit_service:
   dependencies:
     - extensions.circuit
@@ -70,7 +71,7 @@ extensions/cable:
 extensions/circuit:
   dependencies:
     - base
-    - extentions.location_minimal
+    - extensions.location_minimal
   description: This schema extension contains Circuits and ways to connect them with
     your infrastructure! The circuit could be a fiber connecting two sites, you would
     then have two endpoints, one on each site.
@@ -131,7 +132,7 @@ extensions/modules:
   dependencies:
     - base
   description: |
-    This schema extension allows you to capture Device Modules related information like the serial number or the satus. You can insert the Module into a Dcim Physcial Device.
+    This schema extension allows you to capture Device Modules related information like the serial number or the status. You can insert the Module into a Dcim Physical Device.
 
     > [!NOTE]
     > This extension doesn't contain any Node, you can use the extension module_linecards or modules_routing_engine to use it
@@ -141,21 +142,21 @@ extensions/modules_linecards:
     - base
     - extensions.modules
   description: This schema extension allows you to capture Linecard related information
-    like the version. You can insert the Linecard into a Dcim Physcial Device and
+    like the version. You can insert the Linecard into a Dcim Physical Device and
     leverage the Linecard type model. The Linecard can accept PIC to help configure
-    PORT informations like breakout-capabilities and configurations.
+    PORT information like breakout-capabilities and configurations.
   name: Linecards
 extensions/modules_routing_engine:
   dependencies:
     - base
     - extensions.modules
   description: This schema extension allows you to capture Routing Engine related
-    information like the version. You can insert the Routing Engine into a Dcim Physcial
+    information like the version. You can insert the Routing Engine into a Dcim Physical
     Device and leverage the Routing Engine type model.
   name: Routing Engine
 extensions/patch_panel:
   description: |
-    This schema extension allows you to capture patch pannel related information like rear/front interfaces and mapping between them. You can insert the patch panel into a rack and leverage the device type model. Finally you can also capture informations about potential modules you would insert into your patch panel.
+    This schema extension allows you to capture patch panel related information like rear/front interfaces and mapping between them. You can insert the patch panel into a rack and leverage the device type model. Finally you can also capture information about potential modules you would insert into your patch panel.
 
     > [!NOTE]
     > This extension is compatible with all sort of connectors, meaning you can plug cable, circuits, cross-connect to front & rear interfaces!
@@ -217,7 +218,7 @@ extensions/routing_bgp_rr:
     - base
     - extensions.routing
     - extensions.routing_bgp
-  description: This schema extension extemd the BGP extension to add BGP Route Reflector
+  description: This schema extension extend the BGP extension to add BGP Route Reflector
     Clustering.
   name: BGP Route Reflector
 extensions/routing_ospf:
@@ -275,7 +276,7 @@ extensions/routing_policies_pim:
     - extensions.routing_policies
     - extensions.routing_pim
   description: This schema inherits the `RoutingPolicy` schema and removes `import_policies`
-    and `export_policies` attributes. However it adds a number of relatopnships to
+    and `export_policies` attributes. However it adds a number of relationships to
     `RoutingPIM`.
   name: Routing Policies (PIM)
 extensions/sfp: