diff --git a/content/pymesh/_index.md b/content/pymesh/_index.md
index ad32a122..d1dda566 100644
--- a/content/pymesh/_index.md
+++ b/content/pymesh/_index.md
@@ -14,7 +14,7 @@ A Mesh network acts like a net, this means that any node within the network can
 
 Mesh networks essentially get rid of gateways, which decentralises the network's infrastructure. This then means that the network becomes flexible, so it can do many wonderful things – such as generate, change and fix itself. The success of the Mesh network is down to its parts, as any node within the network will automatically connect to the best radio-link available.
 
-Pymesh solution works on all of our LoRa supporting development boards, the LoPy4 and FiPy as well as on our OEM modules, L01 and L04.
+Pymesh works on all of our LoRa supporting development boards, the LoPy4 and FiPy as well as on our OEM modules, L01 and L04.
 
 _**Note: For obtaining the Pymesh firmware please follow the steps from [Pymesh LICENCE page](/pymesh/licence).**_
 
diff --git a/content/pymesh/lib-ble-rpc.md b/content/pymesh/lib-ble-rpc.md
index faa9a1a0..0f4c6ae8 100644
--- a/content/pymesh/lib-ble-rpc.md
+++ b/content/pymesh/lib-ble-rpc.md
@@ -44,7 +44,7 @@ This returns the list of pairs that form a mesh connection, as shown bellow:
 
 #### get_node_info(mac_id = ' ')
 
-This returns the node data for a specified mac address, or own data id `mac_id` is not specified. Node data is dictionary with the following structure:
+This returns the node data for a specified mac address, or own data if `mac_id` is not specified. Node data is dictionary with the following structure:
 ```        
 {
     'ip': 4c00,   # last 2bytes from the ip v6 RLOC16 address
diff --git a/content/pymesh/licence.md b/content/pymesh/licence.md
index 0707fa0f..90a6979b 100644
--- a/content/pymesh/licence.md
+++ b/content/pymesh/licence.md
@@ -7,9 +7,8 @@ aliases:
 ## Licensing process
 
 In order to receive access to the Pymesh firmware releases (for Lopy4, Fipy, L01 or L04), the next process should be followed:
-<!-- <a href="/gitbook/assets/specsheets/Pycom_002_Specsheets_LoPy4_v2.pdf" target="\_blank"> the Pymesh LICENCE PDF document </a> -->
 
-1. Complete the Pymesh LICENCE PDF document(not yet available), sign it and send us by [this email](mailto:catalin@pycom.io?subject=[Pymesh_LICENCE]).
+1. Complete the <a href="/gitbook/assets/pymesh/Pymesh_Licence_Copyright_Notice.pdf" target="\_blank"> the Pymesh LICENCE PDF document</a>, sign it and send us by [this email](mailto:catalin@pycom.io?subject=[Pymesh_LICENCE]).
 1. You will receive by email an archive containing the images for all boards.
 1. Extract the corresponding image, for example Lopy4.tar.gz, and upload the firmware to your board, using the [Pycom Firmware Update Tool](https://pycom.io/downloads/), similar in the following image:
 <img src="/gitbook/assets/pymesh/pymesh_firmware_update.png" alt="Pymesh Firmware Update" width="500"/>
diff --git a/static/gitbook/assets/pymesh/Pymesh_Licence_Copyright_Notice.pdf b/static/gitbook/assets/pymesh/Pymesh_Licence_Copyright_Notice.pdf
new file mode 100644
index 00000000..6843a2ac
Binary files /dev/null and b/static/gitbook/assets/pymesh/Pymesh_Licence_Copyright_Notice.pdf differ