Update according to https://www.grammarly.com/blog/licence-license/

docs/mkdocs.yml

@@ -33,13 +33,13 @@ nav:
  - Index: 'index.md'
  - BSP:
     - 'Overview': 'overview.md'
-    - 'License Information': 'licenses.md'
+    - 'Licence Information': 'licenses.md'
     - 'Quickstart': 'quickstart.md'
     - 'Package Management': 'package-management.md'
     - 'Setting up and using the Build-Environment': 'build-system.md'
     - 'Booting an Image on your Hardware': 'booting-an-image.md'
     - 'Using Qt-Cross-Toolchain and QtCreator': 'qt-cross-dev.md'
-    - 'Exceet Tools and Demos': 'exceet-applications.md'
+    - 'Kontron Tools and Demos': 'exceet-applications.md'
     - 'Using the Hardware': 'using-the-hardware.md'
     - 'Known Issues': 'known-issues.md'
  - Demo Hardware:

docs/src/licenses.md

 # Software licensing
 
-## Licenses of Software Packages
-The software for this board (BSP) contains open-source software with license agreements that, among other things, restrict linking against closed-source applications (e.g. GPL, LGPL). Before using any of the libraries or applications,
-it is therefore necessary to check the license agreements of the used source code. The licenses are contained within the source code of the software packages. Furthermore it is necessary to check any valid patents and license
-conditions of the used software, especially for multimedia formats (e.g. mp3 format). Kontron Electronics GmbH does not assume any liability for infringements of patents or license agreements of parts of the provided BSP.  
-Inside the Yocto build system you find a directory in `<builddir>/tmp/deploy/licenses`, that holds copies of all the licenses of the packages, that were built.  
-To get a list of all the packages and their licenses included in your image, you can look at the file `license.manifest` in `<builddir>/tmp/deploy/licenses/<full-image-name>`.  
+## Licences of Software Packages
+The software for this board (BSP) contains open-source software with licence agreements that, among other things, restrict linking against closed-source applications (e.g. GPL, LGPL). Before using any of the libraries or applications,
+it is therefore necessary to check the licence agreements of the used source code. The licences are contained within the source code of the software packages. Furthermore it is necessary to check any valid patents and licence
+conditions of the used software, especially for multimedia formats (e.g. mp3 format). Kontron Electronics GmbH does not assume any liability for infringements of patents or licence agreements of parts of the provided BSP.  
+Inside the Yocto build system you find a directory in `<builddir>/tmp/deploy/licenses`, that holds copies of all the licences of the packages, that were built.  
+To get a list of all the packages and their licences included in your image, you can look at the file `license.manifest` in `<builddir>/tmp/deploy/licenses/<full-image-name>`.  
 
 If you have no access to those files, feel free to ask Kontron Electronics to provide them for you.
 
-## Typical open-source licenses
-Here are some notes and further information on different licenses.  
+## Typical open-source licences
+Here are some notes and further information on different licences.  
 
 !!! Warning
     The information in this chapter does not make any claim to be complete or to be legally correct.
@@ -18,9 +18,9 @@ Here are some notes and further information on different licenses.
 ### [GPLv2](http://www.gnu.org/licenses/old-licenses/gpl-2.0.html) used by the Linux kernel and many other packages
 
 If you release or redistribute a product, that includes software under GPLv2, you are bound to provide the source code of those parts with your product (copyleft).  
-You can either include the source code with your product and deliver it together, or you can include a written offer to provide the source code when requested.    
+You can either include the source code with your product and deliver it together, or you can include a written offer to provide the source code when requested.  
 * Attention: GPLv2 does not allow you to provide the source code via a network service (e.g as download). You must deliver it on physical media. Only GPLv3 allows delivery via downloads.  
-* Many GPLv2 licensed packages include the possibility to license it under a later version of the same license (e.g. GPLv3), but the Linux kernel for example is GPLv2 only.  
+* Many GPLv2 licensed packages include the possibility to license it under a later version of the same licence (e.g. GPLv3), but the Linux kernel for example is GPLv2 only.  
 If you use code inside your application that is licensed under the GPL you must not keep your application code closed, you are obligated to use the GPL and have to provide the programs source code to your customers.  
 * [Frequently Asked Questions (FAQ)](http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLRequireSourcePostedPublic)  
 * [A Practical Guide to GPL Compliance](https://softwarefreedom.org/resources/2008/compliance-guide.html)  
@@ -41,32 +41,32 @@ The LGPLv3 is the modernized and updated version of the LGPLv2.
 
 ### [MIT](https://opensource.org/licenses/MIT)
 
-The MIT license even allows you to modify and distribute software packages, without the need to publish the source code (no copyleft). It is still necessary to include the license notice in your product.
+The MIT licence even allows you to modify and distribute software packages, without the need to publish the source code (no copyleft). It is still necessary to include the licence notice in your product.
 
 ### [BSD](https://en.wikipedia.org/wiki/BSD_licenses)
   
-The BSD license is similar to the MIT license and has no copyleft.
+The BSD licence is similar to the MIT licence and has no copyleft.
 
-### Proprietary licenses (e.g Freescale/NXP or other HW manufacturers)
+### Proprietary licences (e.g Freescale/NXP or other HW manufacturers)
 
-The BSP might also contain packages, firmware or drivers, that are licensed under proprietary licenses by the manufacturer or other third parties. Depending on your product, those agreements need to be checked for compliance.  
+The BSP might also contain packages, firmware or drivers, that are licensed under proprietary licences by the manufacturer or other third parties. Depending on your product, those agreements need to be checked for compliance.  
 
-## License compliance
+## Licence compliance
 
 !!! Warning
     The information in this chapter does not make any claim to be complete or to be legally correct.
 
-It is essential to make sure, that your final product complies with all the licenses of the included software packages. As mentioned in the last paragraph it depends on the used licenses what you have to do for a full license compliance.  
+It is essential to make sure, that your final product complies with all the licences of the included software packages. As mentioned in the last paragraph it depends on the used licences what you have to do for a full licence compliance.  
 
 ### Notification in the manual
 
-Almost all licenses require that you inform your customers in your manual that you use open-source software.
-You have to mention that parts of your software are open-source software and deliver a list of the components you are using and their particular licenses.  
+Almost all licences require that you inform your customers in your manual that you use open-source software.
+You have to mention that parts of your software are open-source software and deliver a list of the components you are using and their particular licences.  
 
 ### Source code delivery
 
-If you are using software licensed as GPL or LGPL you have to deliver the source code and license texts of this software to your customers or at least, make it possible that your customer can get it. There a several options to achieve this.  
-- Direct delivery with your product: You can accompany your product with a volume containing all used source code under the mentioned licenses.  
+If you are using software licensed as GPL or LGPL you have to deliver the source code and licence texts of this software to your customers or at least, make it possible that your customer can get it. There a several options to achieve this.  
+- Direct delivery with your product: You can accompany your product with a volume containing all used source code under the mentioned licences.  
 - Written offer: You can state in your manual that every customer of your product can get a copy of the source code as long as the delivery of your product is no longer ago than three years or as long as you deliver spare parts.
 It is allowed to ask for a small fee to cover your expenses.  
 - Download (For (L)GPL V3 code only): You can send your customers a link where they can download the source code. You have to guarantee that the link will be accessible for the same time as it would be for the written offer.  
@@ -77,7 +77,7 @@ Please be aware that we only can integrate the source code of the programs we ha
 ### Adding own software to your product
 
 If you are using (L)GPL in version 3 licensed code you have, for version 2 it is recommended, to give your customer the opportunity to install his own programs on your product.
-For code under (L)GPL version 3 you are obligated to grant your customer the right to install his own programs on your product. Version 2 of the license only recommends, but does not enforce this.
+For code under (L)GPL version 3 you are obligated to grant your customer the right to install his own programs on your product. Version 2 of the licence only recommends, but does not enforce this.
 To ensure the security of your device, this opportunity does not have to be included in your product from the beginning, it is appropriate to require your customer to send the product back to you and you will disable the necessary security features
 to allow the installation of custom programs. You can demand that all given warranties of your product will expire at the time of applying custom software.  
 
@@ -95,7 +95,7 @@ Including the statement of the following product data:
 [Serial number]  
 [Date of delivery]  
 We also require a fee of EUR 10,- for the costs of preparation of the medium and shipping to be transferred to the following bank account [Bank account]  
-Preventive it should be mentioned here that using the right of installing own versions of the open-source software components, which is guaranteed in the license contract, will expire all certifications and warranties of the product.
+Preventive it should be mentioned here that using the right of installing own versions of the open-source software components, which is guaranteed in the licence contract, will expire all certifications and warranties of the product.
 The operation of the manipulated product will happen on one's own authority.  
 
 **German**:  
@@ -119,7 +119,7 @@ Unpack the archive in the yocto main folder. Setup your environment and download
 If you have questions, please contact support@kontron.de.   
 
 ## Using Qt in a Product
-There are several licensing options for Qt. You should decide on one of them before starting to design your application, as switching from the open-source license to the commercial license is not allowed.  
+There are several licensing options for Qt. You should decide on one of them before starting to design your application, as switching from the open-source licence to the commercial licence is not allowed.  
 
 Here are some sources for further information:  
 * [Qt Licensing](http://doc.qt.io/qt-5/licensing.html)