diff --git a/config.toml b/config.toml
index f57d527..a8f2798 100644
--- a/config.toml
+++ b/config.toml
@@ -1455,8 +1455,8 @@ theme = "doc-theme"
 
  [[menu.main]]
      name = "Pymesh Integration"
-     url = "/pybytes/pymeshIntegration/"
-     identifier = "pybytes@pymeshIntegration"
+     url = "/pybytes/pymeshintegration/"
+     identifier = "pybytes@pymeshintegration"
      parent = "pybytes"
      weight = 90
 
diff --git a/content/pybytes/pymeshIntegration/_index.md b/content/pybytes/pymeshIntegration/_index.md
index cd44e59..0abefc8 100644
--- a/content/pybytes/pymeshIntegration/_index.md
+++ b/content/pybytes/pymeshIntegration/_index.md
@@ -7,6 +7,6 @@ This documentation is a quick introduction to the new Pymesh integration feature
 
 The Pymesh integration is here to help Pymesh firmware deployment and to monitor Pymesh node's health.
 
-[**Pymesh Provisioning**](/pybytes/pymesh/provisioning)
+[**Pymesh Provisioning**](/pybytes/pymeshintegration/provisioning)
 
-[**Pymesh Monitoring**](/pybytes/pymesh/monitoring)
+[**Pymesh Monitoring**](/pybytes/pymeshintegration/monitoring)
diff --git a/content/pybytes/pymeshIntegration/monitoring.md b/content/pybytes/pymeshIntegration/monitoring.md
index b8cd97c..7a341b7 100644
--- a/content/pybytes/pymeshIntegration/monitoring.md
+++ b/content/pybytes/pymeshIntegration/monitoring.md
@@ -14,4 +14,4 @@ If the user clicks on the devices and go to the **Signal** interface, the user c
 
 ![Devices Signal](/gitbook/assets/pybytes/pymesh/device_signal.png)
 
-To illustrate the Pymesh Provisioning, check [**Pymesh Provisioning**](/pybytes/pymesh/provisioning)
+To illustrate the Pymesh Provisioning, check [**Pymesh Provisioning**](/pybytes/pymeshintegration/provisioning)
diff --git a/content/pybytes/pymeshIntegration/provisioning.md b/content/pybytes/pymeshIntegration/provisioning.md
index 6ea9848..1044220 100644
--- a/content/pybytes/pymeshIntegration/provisioning.md
+++ b/content/pybytes/pymeshIntegration/provisioning.md
@@ -11,7 +11,7 @@ In the screen below there are 2 previously set up projects. Let's go first with
 
 Is possible to create one Pymesh per project.
 
-Once clicking on Create Pymesh button, we are going to be guided through a wizard, where we are going to set up the new Pymesh in 4 steps.
+Once clicking on **Create Pymesh** button, the user will be guided through a wizard, where will be guided to set up the new Pymesh in 4 steps.
 
 ![Create Pymesh](/gitbook/assets/pybytes/pymesh/pymesh_provisioning_create_pymesh.png)
 
@@ -31,7 +31,7 @@ All devices eligible to be part of a Pymesh, will be under this list. The user s
 
 #### The third step is the Pymesh Settings.
 
-All parameters are filled with default values, if you need to change it, it's possible.
+All parameters are filled with default values, if the user needs to change it, it's possible.
 
 If all the parameters are ok, the user should generate the join-key, and go ahead.
 
@@ -49,9 +49,9 @@ Here the user can check if all information is correct. If everything is fine, th
 
 ### And here is the Pymesh.
 
-On this interface, the user can add or remove devices from the Pymesh, we also can go to configuration, and change the Pymesh settings if it is necessary.
+On this interface, the user can add or remove devices from the Pymesh. The user can also go to configuration, and change the Pymesh settings if it is necessary.
 
-To deploy the Pymesh Settings and Pymesh Firmware into the devices, let's click on the **Deploy Pymesh** button.
+To deploy the Pymesh Settings and Pymesh Firmware into the devices, click on the **Deploy Pymesh** button.
 
 ![Pymesh](/gitbook/assets/pybytes/pymesh/pymesh_monitoring_struct.png)
 
@@ -63,4 +63,4 @@ Now the device is properly configured with the Pymesh settings and Pymesh firmwa
 
 All the user needs to do is implement their own script on the well-know **main.py** file.
 
-To illustrate the Pymesh behavior, check [**Pymesh Monitoring**](/pybytes/pymesh/monitoring)
+To illustrate the Pymesh behavior, check [**Pymesh Monitoring**](/pybytes/pymeshintegration/monitoring)