diff --git a/docs-gen/content/license/_index.md b/docs-gen/content/license/_index.md
index f7d41c2dd..029a639b5 100644
--- a/docs-gen/content/license/_index.md
+++ b/docs-gen/content/license/_index.md
@@ -18,7 +18,7 @@ We will line out some answers to commonly asked questions, but keep in mind this
 Most definitely yes. You must inform your users that the product contains MPLed code and need to provide access to the source (e.g. by linking to this documentation or our [Github repository](https://github.com/covesa/vehicle_signal_specification)).
 
 ## I modified VSS-tools, do I need to give away my source?
-If you use the code internally within your organisation (company), you have no obligations to do so. (see also [Q5 here](https://www.mozilla.org/en-US/MPL/2.0/FAQ/)). If you distribute the modified vss-tools outside your organization (e.g. to your customers), you need to make the source code of the MPL-2.0 licensed parts available.  However, the MPL has only a very weak copyleft effect. As a rule of thumb: You have no obligation to provide code in new files. You have the obligation to make code of changed existing MPLed files available under the clauses pof the MPL-2.0, _if_ you distribute them in source or compiled form outside your organisation ((see also [Q9,10,11 here](https://www.mozilla.org/en-US/MPL/2.0/FAQ/))).
+If you use the code internally within your organisation (company), you have no obligations to do so. (see also [Q5 here](https://www.mozilla.org/en-US/MPL/2.0/FAQ/)). If you distribute the modified vss-tools outside your organization (e.g. to your customers), you need to make the source code of the MPL-2.0 licensed parts available.  However, the MPL has only a very weak copyleft effect. As a rule of thumb: You have no obligation to provide code in new files. You have the obligation to make code of changed existing MPLed files available under the clauses of the MPL-2.0, _if_ you distribute them in source or compiled form outside your organisation ((see also [Q9,10,11 here](https://www.mozilla.org/en-US/MPL/2.0/FAQ/))).
 
 In any case we _do_ recommend you to consider sharing generally useful improvements with the community. Not only will you win karma points with the community and gain visibility as an innovation leader in the automotive industry, you will most likely also get more robust software as you will have more users and testers.