fixup! Fixes #15008: Add a \"Rudder by example\" to add CPU vulnerabi…

…lities status to inventory

Fixes #15008: Add a \"Rudder by example\" to add CPU vulnerabilities status to inventory

src/rudder-by-example/modules/ROOT/pages/system/extend-inventories.adoc

@@ -31,7 +31,7 @@ To be able to use our custom data we need to:
 
 An inventory extension script can be written in any language, it just needs to be an
 executable file placed in `/var/rudder/hooks.d` that outputs a json object. It will be called at each 
-inventory,and its output will be added into it.
+inventory, and its output will be added into it.
 
 NOTE: Read the xref:reference:usage:advanced_node_management.adoc#extend-nodes-inventory[dedicated section]
 for more details.
@@ -43,7 +43,7 @@ rework it to make it easily usable on the server. We'll:
 * Determine the status of the node for each known vulnerability
 * Add details in a separate variable for mode advanced handling
 
-In our case, we have write a small python script (the https://github.com/Normation/rudder-tools/blob/master/contrib/inventory-hooks/cpu_vulnerabilities.py[script] and its https://github.com/Normation/rudder-tools/blob/master/contrib/inventory-hooks/cpu_vulnerabilities.adoc[documentation]) that outputs our CPU vulnerabilities in the
+In our case, we have written a small python script (the https://github.com/Normation/rudder-tools/blob/master/contrib/inventory-hooks/cpu_vulnerabilities.py[script] and its https://github.com/Normation/rudder-tools/blob/master/contrib/inventory-hooks/cpu_vulnerabilities.adoc[documentation]) that outputs our CPU vulnerabilities in the
 following format:
 
 [source,json]