GitBook: [master] 333 pages modified

Alami-Amine · Nov 22, 2018 · ac606b6 · ac606b6
1 parent 6f9eea4
commit ac606b6
Show file tree

Hide file tree

Showing 170 changed files with 331 additions and 361 deletions.
diff --git a/README.md b/README.md
@@ -5,10 +5,10 @@ Welcome to the Pycom documentation site. We recommend reading through all the se
 To get started, read through the Getting Started Guide then feel free to jump straight into the tutorials and examples in Tutorials & Examples to begin building your projects.
 
 * [Products](products.md)
-* [Getting Started](gettingstarted/introduction.md)
-* [Pymakr](pymakr/installation/)
-* [Tutorials](tutorials/introduction.md)
-* [API Documentation](firmwareapi/introduction.md)
-* [Product Info](datasheets/introduction.md)
+* [Getting Started](getting-started/introduction.md)
+* [Pymakr](pymakr-plugin/installation/)
+* [Tutorials](tutorials-and-examples/introduction.md)
+* [API Documentation](firmware-and-api-reference/introduction.md)
+* [Product Info](product-info-datasheets/introduction.md)
 * [Pybytes](pybytes/introduction.md)
 
diff --git a/SUMMARY.md b/SUMMARY.md
diff --git a/advance/cli.md → advanced-topics/cli.md b/advance/cli.md → advanced-topics/cli.md
@@ -325,7 +325,7 @@ To restore your OTA block: `$pycom-fwtool-cli -p PORT ota -r -f backup.ota`
 
 #### lpwan
 
-Get/Set LPWAN parameters saved to non-volatile storage. Please see [here](../firmwareapi/pycom/network/lora.md##loranvramsave) for more details.
+Get/Set LPWAN parameters saved to non-volatile storage. Please see [here](../firmware-and-api-reference/pycom/network/lora.md##loranvramsave) for more details.
 
 ```text
 usage: pycom-fwtool-cli  -p PORT lpwan [-h] [--region REGION]

diff --git a/advance/downgrade.md → advanced-topics/downgrade.md b/advance/downgrade.md → advanced-topics/downgrade.md
diff --git a/advance/encryption.md → advanced-topics/encryption.md b/advance/encryption.md → advanced-topics/encryption.md
diff --git a/docnotes/introduction.md → documentation-notes/introduction.md b/docnotes/introduction.md → documentation-notes/introduction.md
diff --git a/docnotes/mesh-networks.md → documentation-notes/mesh-networks.md b/docnotes/mesh-networks.md → documentation-notes/mesh-networks.md
diff --git a/docnotes/replscript.md → documentation-notes/replscript.md b/docnotes/replscript.md → documentation-notes/replscript.md
diff --git a/docnotes/syntax.md → documentation-notes/syntax.md b/docnotes/syntax.md → documentation-notes/syntax.md
diff --git a/firmwareapi/introduction.md → firmware-and-api-reference/introduction.md b/firmwareapi/introduction.md → firmware-and-api-reference/introduction.md
diff --git a/firmwareapi/micropython/README.md → ...e-and-api-reference/micropython/README.md b/firmwareapi/micropython/README.md → ...e-and-api-reference/micropython/README.md
diff --git a/firmwareapi/micropython/_thread.md → ...-and-api-reference/micropython/_thread.md b/firmwareapi/micropython/_thread.md → ...-and-api-reference/micropython/_thread.md
diff --git a/firmwareapi/micropython/array.md → ...re-and-api-reference/micropython/array.md b/firmwareapi/micropython/array.md → ...re-and-api-reference/micropython/array.md
diff --git a/firmwareapi/micropython/builtin.md → ...-and-api-reference/micropython/builtin.md b/firmwareapi/micropython/builtin.md → ...-and-api-reference/micropython/builtin.md
diff --git a/firmwareapi/micropython/cmath.md → ...re-and-api-reference/micropython/cmath.md b/firmwareapi/micropython/cmath.md → ...re-and-api-reference/micropython/cmath.md
diff --git a/firmwareapi/micropython/gc.md → firmware-and-api-reference/micropython/gc.md b/firmwareapi/micropython/gc.md → firmware-and-api-reference/micropython/gc.md
diff --git a/firmwareapi/micropython/math.md → ...are-and-api-reference/micropython/math.md b/firmwareapi/micropython/math.md → ...are-and-api-reference/micropython/math.md
diff --git a/firmwareapi/micropython/micropython.md → ...-api-reference/micropython/micropython.md b/firmwareapi/micropython/micropython.md → ...-api-reference/micropython/micropython.md
diff --git a/firmwareapi/micropython/select.md → ...e-and-api-reference/micropython/select.md b/firmwareapi/micropython/select.md → ...e-and-api-reference/micropython/select.md
diff --git a/firmwareapi/micropython/sys.md → ...ware-and-api-reference/micropython/sys.md b/firmwareapi/micropython/sys.md → ...ware-and-api-reference/micropython/sys.md
diff --git a/firmwareapi/micropython/ubinascii.md → ...nd-api-reference/micropython/ubinascii.md b/firmwareapi/micropython/ubinascii.md → ...nd-api-reference/micropython/ubinascii.md
diff --git a/firmwareapi/micropython/ucrypto.md → ...-and-api-reference/micropython/ucrypto.md b/firmwareapi/micropython/ucrypto.md → ...-and-api-reference/micropython/ucrypto.md
diff --git a/firmwareapi/micropython/uctypes.md → ...-and-api-reference/micropython/uctypes.md b/firmwareapi/micropython/uctypes.md → ...-and-api-reference/micropython/uctypes.md
diff --git a/firmwareapi/micropython/uhashlib.md → ...and-api-reference/micropython/uhashlib.md b/firmwareapi/micropython/uhashlib.md → ...and-api-reference/micropython/uhashlib.md
diff --git a/firmwareapi/micropython/ujson.md → ...re-and-api-reference/micropython/ujson.md b/firmwareapi/micropython/ujson.md → ...re-and-api-reference/micropython/ujson.md
diff --git a/firmwareapi/micropython/uos.md → ...ware-and-api-reference/micropython/uos.md b/firmwareapi/micropython/uos.md → ...ware-and-api-reference/micropython/uos.md
diff --git a/firmwareapi/micropython/ure.md → ...ware-and-api-reference/micropython/ure.md b/firmwareapi/micropython/ure.md → ...ware-and-api-reference/micropython/ure.md
diff --git a/firmwareapi/micropython/usocket.md → ...-and-api-reference/micropython/usocket.md b/firmwareapi/micropython/usocket.md → ...-and-api-reference/micropython/usocket.md
diff --git a/firmwareapi/micropython/ussl.md → ...are-and-api-reference/micropython/ussl.md b/firmwareapi/micropython/ussl.md → ...are-and-api-reference/micropython/ussl.md
diff --git a/firmwareapi/micropython/ustruct.md → ...-and-api-reference/micropython/ustruct.md b/firmwareapi/micropython/ustruct.md → ...-and-api-reference/micropython/ustruct.md
diff --git a/firmwareapi/micropython/utime.md → ...re-and-api-reference/micropython/utime.md b/firmwareapi/micropython/utime.md → ...re-and-api-reference/micropython/utime.md
diff --git a/firmwareapi/notes.md → firmware-and-api-reference/notes.md b/firmwareapi/notes.md → firmware-and-api-reference/notes.md
diff --git a/firmwareapi/pycom/README.md → firmware-and-api-reference/pycom/README.md b/firmwareapi/pycom/README.md → firmware-and-api-reference/pycom/README.md
diff --git a/firmwareapi/pycom/aes.md → firmware-and-api-reference/pycom/aes.md b/firmwareapi/pycom/aes.md → firmware-and-api-reference/pycom/aes.md
diff --git a/firmwareapi/pycom/machine/README.md → ...and-api-reference/pycom/machine/README.md b/firmwareapi/pycom/machine/README.md → ...and-api-reference/pycom/machine/README.md
diff --git a/firmwareapi/pycom/machine/adc.md → ...re-and-api-reference/pycom/machine/adc.md b/firmwareapi/pycom/machine/adc.md → ...re-and-api-reference/pycom/machine/adc.md
diff --git a/firmwareapi/pycom/machine/can.md → ...re-and-api-reference/pycom/machine/can.md b/firmwareapi/pycom/machine/can.md → ...re-and-api-reference/pycom/machine/can.md
diff --git a/firmwareapi/pycom/machine/dac.md → ...re-and-api-reference/pycom/machine/dac.md b/firmwareapi/pycom/machine/dac.md → ...re-and-api-reference/pycom/machine/dac.md
diff --git a/firmwareapi/pycom/machine/i2c.md → ...re-and-api-reference/pycom/machine/i2c.md b/firmwareapi/pycom/machine/i2c.md → ...re-and-api-reference/pycom/machine/i2c.md
diff --git a/firmwareapi/pycom/machine/pin.md → ...re-and-api-reference/pycom/machine/pin.md b/firmwareapi/pycom/machine/pin.md → ...re-and-api-reference/pycom/machine/pin.md
diff --git a/firmwareapi/pycom/machine/pwm.md → ...re-and-api-reference/pycom/machine/pwm.md b/firmwareapi/pycom/machine/pwm.md → ...re-and-api-reference/pycom/machine/pwm.md
diff --git a/firmwareapi/pycom/machine/rmt.md → ...re-and-api-reference/pycom/machine/rmt.md b/firmwareapi/pycom/machine/rmt.md → ...re-and-api-reference/pycom/machine/rmt.md
diff --git a/firmwareapi/pycom/machine/rtc.md → ...re-and-api-reference/pycom/machine/rtc.md b/firmwareapi/pycom/machine/rtc.md → ...re-and-api-reference/pycom/machine/rtc.md
diff --git a/firmwareapi/pycom/machine/sd.md → ...are-and-api-reference/pycom/machine/sd.md b/firmwareapi/pycom/machine/sd.md → ...are-and-api-reference/pycom/machine/sd.md
diff --git a/firmwareapi/pycom/machine/spi.md → ...re-and-api-reference/pycom/machine/spi.md b/firmwareapi/pycom/machine/spi.md → ...re-and-api-reference/pycom/machine/spi.md
diff --git a/firmwareapi/pycom/machine/timer.md → ...-and-api-reference/pycom/machine/timer.md b/firmwareapi/pycom/machine/timer.md → ...-and-api-reference/pycom/machine/timer.md
diff --git a/firmwareapi/pycom/machine/uart.md → ...e-and-api-reference/pycom/machine/uart.md b/firmwareapi/pycom/machine/uart.md → ...e-and-api-reference/pycom/machine/uart.md
diff --git a/firmwareapi/pycom/machine/wdt.md → ...re-and-api-reference/pycom/machine/wdt.md b/firmwareapi/pycom/machine/wdt.md → ...re-and-api-reference/pycom/machine/wdt.md
diff --git a/firmwareapi/pycom/network/README.md → ...and-api-reference/pycom/network/README.md b/firmwareapi/pycom/network/README.md → ...and-api-reference/pycom/network/README.md
diff --git a/...wareapi/pycom/network/bluetooth/README.md → ...ference/pycom/network/bluetooth/README.md b/...wareapi/pycom/network/bluetooth/README.md → ...ference/pycom/network/bluetooth/README.md
diff --git a/firmwareapi/pycom/network/bluetooth/gatt.md → ...reference/pycom/network/bluetooth/gatt.md b/firmwareapi/pycom/network/bluetooth/gatt.md → ...reference/pycom/network/bluetooth/gatt.md
diff --git a/.../network/bluetooth/gattccharacteristic.md → .../network/bluetooth/gattccharacteristic.md b/.../network/bluetooth/gattccharacteristic.md → .../network/bluetooth/gattccharacteristic.md
diff --git a/...ycom/network/bluetooth/gattcconnection.md → ...ycom/network/bluetooth/gattcconnection.md b/...ycom/network/bluetooth/gattcconnection.md → ...ycom/network/bluetooth/gattcconnection.md
diff --git a/.../pycom/network/bluetooth/gattccservice.md → .../pycom/network/bluetooth/gattccservice.md b/.../pycom/network/bluetooth/gattccservice.md → .../pycom/network/bluetooth/gattccservice.md
diff --git a/.../network/bluetooth/gattscharacteristic.md → .../network/bluetooth/gattscharacteristic.md b/.../network/bluetooth/gattscharacteristic.md → .../network/bluetooth/gattscharacteristic.md
diff --git a/...i/pycom/network/bluetooth/gattsservice.md → ...e/pycom/network/bluetooth/gattsservice.md b/...i/pycom/network/bluetooth/gattsservice.md → ...e/pycom/network/bluetooth/gattsservice.md
diff --git a/firmwareapi/pycom/network/lora.md → ...e-and-api-reference/pycom/network/lora.md b/firmwareapi/pycom/network/lora.md → ...e-and-api-reference/pycom/network/lora.md
diff --git a/firmwareapi/pycom/network/lte.md → ...re-and-api-reference/pycom/network/lte.md b/firmwareapi/pycom/network/lte.md → ...re-and-api-reference/pycom/network/lte.md
@@ -12,7 +12,7 @@ The GPy and FiPy support both new LTE-M protocols:
 {% endhint %}
 
 {% hint style="info" %}
-The Sequans modem used on Pycom's cellular enabled modules can only work in one of these modes at a time. In order to switch between the two protocols you need to flash a different firmware to the Sequans modem. Instructions for this can be found [here](../../../tutorials/lte/firmware.md).
+The Sequans modem used on Pycom's cellular enabled modules can only work in one of these modes at a time. In order to switch between the two protocols you need to flash a different firmware to the Sequans modem. Instructions for this can be found [here](../../../tutorials-and-examples/lte/firmware.md).
 {% endhint %}
 
 ## AT Commands

diff --git a/firmwareapi/pycom/network/server.md → ...and-api-reference/pycom/network/server.md b/firmwareapi/pycom/network/server.md → ...and-api-reference/pycom/network/server.md
diff --git a/firmwareapi/pycom/network/sigfox.md → ...and-api-reference/pycom/network/sigfox.md b/firmwareapi/pycom/network/sigfox.md → ...and-api-reference/pycom/network/sigfox.md
diff --git a/firmwareapi/pycom/network/wlan.md → ...e-and-api-reference/pycom/network/wlan.md b/firmwareapi/pycom/network/wlan.md → ...e-and-api-reference/pycom/network/wlan.md
diff --git a/firmwareapi/pycom/pycom.md → firmware-and-api-reference/pycom/pycom.md b/firmwareapi/pycom/pycom.md → firmware-and-api-reference/pycom/pycom.md
diff --git a/gettingstarted/connection/README.md → getting-started/connection/README.md b/gettingstarted/connection/README.md → getting-started/connection/README.md
diff --git a/gettingstarted/connection/fipy.md → getting-started/connection/fipy.md b/gettingstarted/connection/fipy.md → getting-started/connection/fipy.md
@@ -13,7 +13,7 @@
 {% endtab %}
 
 {% tab title="Exp Board 3.0" %}
-* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * When using the expansion board with a FiPy, you will need to remove the CTS and RTS jumpers as these interfere with communication with the cellular modem.
 * Look for the reset button on the module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the expansion board.
@@ -23,7 +23,7 @@
 {% endtab %}
 
 {% tab title="Pytrack/Pysense/Pyscan" %}
-* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * Look for the reset button on the FiPy module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the Pysense/Pytrack/Pyscan.
 * Insert the module on the Pysense/Pytrack/Pyscan with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIqVauBuoNMgcByrNql%2FPysense_FiPy.png?generation=1534772069160637&alt=media)![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIqVdDdxkK38AlRxtkc%2FPytrack_FiPy.png?generation=1534772071490748&alt=media)
@@ -96,7 +96,7 @@ If you intend on using the LTE CAT-M1 or NB-IoT connectivity of the FiPy you **m
 
 ### WiFi/Bluetooth \(optional\)
 
-All Pycom modules, including the FiPy, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the FiPy in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmwareapi/pycom/network/wlan.md)
+All Pycom modules, including the FiPy, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the FiPy in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmware-and-api-reference/pycom/network/wlan.md)
 
 ![](../../.gitbook/assets/wifi_pigtail_ant_fipy.png)
 

diff --git a/gettingstarted/connection/gpy.md → getting-started/connection/gpy.md b/gettingstarted/connection/gpy.md → getting-started/connection/gpy.md
@@ -12,7 +12,7 @@
 {% endtab %}
 
 {% tab title="Exp Board 3.0" %}
-* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * Look for the reset button on the module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the expansion board.
 * Insert the GPy module on the Expansion Board with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible.
@@ -21,7 +21,7 @@
 {% endtab %}
 
 {% tab title="Pytrack/Pysense/Pyscan" %}
-* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * Look for the reset button on the GPy module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the Pysense/Pytrack/Pyscan.
 * Insert the module on the Pysense/Pytrack/Pyscan with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIqejpmTIS1tbGw0Vrl%2FPysense_GPy.png?generation=1534772072781141&alt=media)![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIqekpWIfccll6qkt85%2FPytrack_GPy.png?generation=1534772080535030&alt=media)
@@ -73,7 +73,7 @@ If you intend on using the LTE CAT-M1 or NB-IoT connectivity of the GPy you **mu
 
 ### WiFi/Bluetooth \(optional\)
 
-All Pycom modules, including the GPy, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the GPy in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmwareapi/pycom/network/wlan.md)
+All Pycom modules, including the GPy, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the GPy in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmware-and-api-reference/pycom/network/wlan.md)
 
 ![](../../.gitbook/assets/wifi_pigtail_ant_gpy.png)
 

diff --git a/gettingstarted/connection/lopy.md → getting-started/connection/lopy.md b/gettingstarted/connection/lopy.md → getting-started/connection/lopy.md
@@ -12,7 +12,7 @@
 {% endtab %}
 
 {% tab title="Exp Board 3.0" %}
-* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * Look for the reset button on the module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the expansion board.
 * Insert the LoPy module on the Expansion Board with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible.
@@ -21,7 +21,7 @@
 {% endtab %}
 
 {% tab title="Pytrack/Pysense/Pyscan" %}
-* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * Look for the reset button on the LoPy module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the Pysense/Pytrack/Pyscan.
 * Insert the module on the Pysense/Pytrack/Pyscan with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIq_ZvQtB3k9-QzXSEi%2FPysense_LoPy.png?generation=1534772084691543&alt=media)![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIq_aBQabbigN5pR8W2%2FPytrack_LoPy.png?generation=1534772068406423&alt=media)
@@ -84,7 +84,7 @@ The LoPy only supports LoRa on the 868MHz or 915MHz bands. It does not support 4
 
 ### WiFi/Bluetooth \(optional\)
 
-All Pycom modules, including the LoPy, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the LoPy in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmwareapi/pycom/network/wlan.md)
+All Pycom modules, including the LoPy, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the LoPy in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmware-and-api-reference/pycom/network/wlan.md)
 
 ![](../../.gitbook/assets/wifi_pigtail_ant_lopy.png)
 

diff --git a/gettingstarted/connection/lopy4.md → getting-started/connection/lopy4.md b/gettingstarted/connection/lopy4.md → getting-started/connection/lopy4.md
@@ -12,7 +12,7 @@
 {% endtab %}
 
 {% tab title="Exp Board 3.0" %}
-* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * Look for the reset button on the module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the expansion board.
 * Insert the LoPy4 module on the Expansion Board with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible.
@@ -21,7 +21,7 @@
 {% endtab %}
 
 {% tab title="Pytrack/Pysense/Pyscan" %}
-* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * Look for the reset button on the LoPy4 module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the Pysense/Pytrack/Pyscan.
 * Insert the module on the Pysense/Pytrack/Pyscan with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible. 
@@ -86,7 +86,7 @@ Since the LoRa chip only runs on one frequency band at a time you only need to c
 
 ### WiFi/Bluetooth \(optional\)
 
-All Pycom modules, including the LoPy4, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the LoPy4 in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmwareapi/pycom/network/wlan.md)
+All Pycom modules, including the LoPy4, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the LoPy4 in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmware-and-api-reference/pycom/network/wlan.md)
 
 ![](../../.gitbook/assets/wifi_pigtail_ant_lopy4.png)
 
diff --git a/gettingstarted/connection/sipy.md → getting-started/connection/sipy.md b/gettingstarted/connection/sipy.md → getting-started/connection/sipy.md
@@ -12,7 +12,7 @@
 {% endtab %}
 
 {% tab title="Exp Board 3.0" %}
-* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to an Expansion Board 3.0, you should update the firmware on the Expansion Board 3.0. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * Look for the reset button on the module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the expansion board.
 * Insert the SiPy module on the Expansion Board with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible.
@@ -21,7 +21,7 @@
 {% endtab %}
 
 {% tab title="Pytrack/Pysense/Pyscan" %}
-* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrackpysense/installation/firmware.md).
+* Before connecting your module to a Pysense/Pytrack/Pyscan board, you should update the firmware on the Pysense/Pytrack/Pyscan. Instructions on how to do this can be found [here](../../pytrack-pysense-pyscan/installation/firmware.md).
 * Look for the reset button on the SiPy module \(located at a corner of the board, next to the LED\).
 * Locate the USB connector on the Pysense/Pytrack/Pyscan.
 * Insert the module on the Pysense/Pytrack/Pyscan with the reset button pointing towards the USB connector. It should firmly click into place and the pins should now no longer be visible. ![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIqd_e51Wyuw40k6yJv%2FPysense_SiPy.png?generation=1534772077104600&alt=media)![](https://blobscdn.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIfiUlGe6_zTmmvcuEa%2F-LKMXk1KQvBgjpw04I3u%2F-LIqdauW7rAnQlc-AL07%2FPytrack_SiPy.png?generation=1534772072530754&alt=media)
@@ -80,7 +80,7 @@ If you intend on using the Sigfox connectivity of the SiPy you **must** connect
 
 ### WiFi/Bluetooth \(optional\)
 
-All Pycom modules, including the FiPy, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the FiPy in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmwareapi/pycom/network/wlan.md)
+All Pycom modules, including the FiPy, come with a on-board WiFi antenna as well as a U.FL connector for an external antenna. The external antenna is optional and only required if you need better performance or are mounting the FiPy in such a way that the WiFi signal is blocked. Switching between the antennas is done via software, instructions for this can be found [here.](../../firmware-and-api-reference/pycom/network/wlan.md)
 
 ![](../../.gitbook/assets/wifi_pigtail_ant_sipy.png)