diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt
index 5766377..014da0b 100644
--- a/_licenses/cern-ohl-p-2.0.txt
+++ b/_licenses/cern-ohl-p-2.0.txt
@@ -7,7 +7,7 @@ description: The CERN OHL was drafted with hardware in mind. On top of licensin
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
-note: CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product. See the User's Guide for example notices and further explanation.
+note: CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product.
using:
tedium: https://github.com/jboone/tedium/blob/master/LICENSE-CERN-OHL-P-v2
diff --git a/_licenses/cern-ohl-s-2.0.txt b/_licenses/cern-ohl-s-2.0.txt
index 0bb721d..c346e06 100644
--- a/_licenses/cern-ohl-s-2.0.txt
+++ b/_licenses/cern-ohl-s-2.0.txt
@@ -7,7 +7,7 @@ description: The CERN OHL was drafted with hardware in mind. On top of licensin
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
-note: CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product. See the User's Guide for example notices and further explanation.
+note: CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product.
using:
USB Armory: https://github.com/f-secure-foundry/usbarmory/blob/master/hardware/mark-two/LICENSE
diff --git a/_licenses/cern-ohl-w-2.0.txt b/_licenses/cern-ohl-w-2.0.txt
index f9caee4..caa1893 100644
--- a/_licenses/cern-ohl-w-2.0.txt
+++ b/_licenses/cern-ohl-w-2.0.txt
@@ -7,7 +7,7 @@ description: The CERN OHL was drafted with hardware in mind. On top of licensin
how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
-note: CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product. See the User's Guide for example notices and further explanation.
+note: CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product.
using:
Simple PCIe FMC carrier: https://ohwr.org/project/spec/blob/master/LICENSES/CERN-OHL-W-2.0.txt