fix on alert info

content/gettingstarted/_index.md

@@ -32,4 +32,4 @@ Now that you familiar with programming your device you will no doubt be keen to
 
 {{% hint style="info" %}}
 You can navigate through this guide using the arrow buttons at the bottom of the page.
-{{< /hint >}}
+{{% /hint %}}

content/gettingstarted/connection/fipy.md

@@ -115,11 +115,11 @@ aliases:
 
 {{% hint style="danger" %}}
 If you intend on using the LoRa/Sigfox connectivity of the FiPy you **must** connect a LoRa/Sigfox antenna to your FiPy before trying to use LoRa/Sigfox otherwise you risk damaging the device.
-{{< /hint >}}
+{{% /hint %}}
 
 {{% hint style="info" %}}
 The FiPy only supports LoRa on the 868MHz or 915MHz bands. It does not support 433MHz. For this you will require a LoPy4.
-{{< /hint >}}
+{{% /hint %}}
 
 * Firstly you will need to connect the U.FL to SMA pig tail to the FiPy using the U.FL connector on the same side of the FiPy as the LED.
 
@@ -134,7 +134,7 @@ The FiPy only supports LoRa on the 868MHz or 915MHz bands. It does not support 4
 
 {{% hint style="danger" %}}
 If you intend on using the LTE CAT-M1 or NB-IoT connectivity of the FiPy you **must** connect a LTE CAT-M1/NB-IoT antenna to your FiPy before trying to use LTE Cat-M1 or NB-IoT otherwise you risk damaging the device.
-{{< /hint >}}
+{{% /hint %}}
 
 * You will need to connect the antenna to the FiPy using the U.FL connector on the under side of the FiPy.
 

content/gettingstarted/connection/gpy.md

@@ -102,7 +102,7 @@ aliases:
 
 {{% hint style="danger" %}}
 If you intend on using the LTE CAT-M1 or NB-IoT connectivity of the GPy you **must** connect a LTE CAT-M1/NB-IoT antenna to your GPy before trying to use LTE Cat-M1 or NB-IoT otherwise you risk damaging the device.
-{{< /hint >}}
+{{% /hint %}}
 
 * You will need to connect the antenna to the GPy using the U.FL connector on the same side of the GPy as the LED.
 

content/gettingstarted/connection/lopy.md

@@ -115,11 +115,11 @@ aliases:
 
 {{% hint style="danger" %}}
 If you intend on using the LoRa connectivity of the LoPy you **must** connect a LoRa antenna to your LoPy before trying to use LoRa otherwise you risk damaging the device.
-{{< /hint >}}
+{{% /hint %}}
 
 {{% hint style="danger" %}}
 The LoPy only supports LoRa on the 868MHz or 915MHz bands. It does not support 433MHz. For this you will require a LoPy4.
-{{< /hint >}}
+{{% /hint %}}
 
 * Firstly you will need to connect the U.FL to SMA pig tail to the LoPy using the U.FL connector on the same side of the LoPy as the LED.
 

content/gettingstarted/connection/lopy4.md

@@ -115,7 +115,7 @@ aliases:
 
 {{% hint style="danger" %}}
 If you intend on using the LoRa/Sigfox connectivity of the LoPy4 you **must** connect a LoRa/Sigfox antenna to your LoPy4 before trying to use LoRa/Sigfox otherwise you risk damaging the device.
-{{< /hint >}}
+{{% /hint %}}
 
 * Firstly you will need to connect the U.FL to SMA pig tail to the LoPy4 using one of the two the U.FL connectors on the same side of the LoPy4 as the LED. The one on the left hand side is for 433MHz (LoRa only), the one of the right hand side is for 868MHz/915MHz (LoRa & Sigfox). **Note:** This is different from the LoPy.
 
@@ -128,7 +128,7 @@ If you intend on using the LoRa/Sigfox connectivity of the LoPy4 you **must** co
 
 {{% hint style="danger" %}}
 Since the LoRa chip only runs on one frequency band at a time you only need to connect an antenna to the appropriate U.FL connecor. You should be supplied with a the antenna that suits the band you intend using.
-{{< /hint >}}
+{{% /hint %}}
 
 ### WiFi/Bluetooth (optional)
 

content/gettingstarted/connection/sipy.md

@@ -111,7 +111,7 @@ Please ensure you have the signal level of the UART adapter set to
 
 {{% hint style="danger" %}}
 If you intend on using the Sigfox connectivity of the SiPy you **must** connect a Sigfox antenna to your SiPy before trying to use Sigfox otherwise you risk damaging the device.
-{{< /hint >}}
+{{% /hint %}}
 
 * Firstly you will need to connect the U.FL to SMA pig tail to the SiPy using the U.FL connector on the same side of the SiPy as the LED.
 

content/gettingstarted/installation/firmwaretool.md

@@ -16,7 +16,7 @@ Here are the download links to the update tool. Please download the appropriate
 
 {{% hint style="info" %}}
 Previous versions of firmware are available for download [**here**](/advance/downgrade).
-{{< /hint >}}
+{{% /hint %}}
 
 ## Updating Device Firmware
 

content/gettingstarted/programming/examples.md

@@ -119,5 +119,5 @@ print(pycom_devices[0]) # expect 'wipy'
 
 {{% hint style="info" %}}
 For more Python examples, check out these [tutorials](https://www.tutorialspoint.com/python3/). Be aware of the implementation differences between MicroPython and Python 3.5.
-{{< /hint >}}
+{{% /hint %}}
 

content/gettingstarted/programming/first-project.md

@@ -26,7 +26,7 @@ If you are using Atom, it is important to check at this point that Atom has succ
 ![](/gitbook/assets/atom_project.png)
 
 If this is not the case you can press `alt-ctrl-r` on Windows/Linux or `ctrl-alt-cmd-l` on macOS, in order to reload Atom and fix the issue.
-{{< /hint >}}
+{{% /hint %}}
 
 4. Now that you have a project created, we need to add some files to it. A standard MicroPython project has the following structure:
 

content/gettingstarted/programming/micropython.md

@@ -28,5 +28,5 @@ Micropython also has a number of Micropython specific libraries for accessing ha
 Micropython, unlike C/C++ or Arduino, **does not use braces {} to indicate blocks of code** specified for class and function definitions or flow control. Blocks of code are denoted by line indentation, which is strictly enforced.
 
 The number of spaces in the indentation is variable but all statements within a block must be indented the same amount.
-{{< /hint >}}
+{{% /hint %}}
 

content/gettingstarted/programming/repl/README.md

@@ -24,5 +24,5 @@ There are a number of useful shortcuts for interacting with the MicroPython REPL
 * `Ctrl-D` on a blank line will do a soft reset.
 * `Ctrl-E` enters ‘paste mode' that allows you to copy and paste chunks of text. Exit this mode using `Ctrl-D`.
 * `Ctrl-F` performs a "safe-boot" of the device that prevents `boot.py` and `main.py` from executing
-{{< /hint >}}
+{{% /hint %}}
 

content/gettingstarted/programming/repl/_index.md

@@ -23,5 +23,5 @@ There are a number of useful shortcuts for interacting with the MicroPython REPL
 * `Ctrl-D` on a blank line will do a soft reset.
 * `Ctrl-E` enters ‘paste mode' that allows you to copy and paste chunks of text. Exit this mode using `Ctrl-D`.
 * `Ctrl-F` performs a "safe-boot" of the device that prevents `boot.py` and `main.py` from executing
-{{< /hint >}}
+{{% /hint %}}
 

content/gettingstarted/programming/repl/serial.md

@@ -33,7 +33,7 @@ This will allow screen to exited by pressing `CTRL-A Q`.
 
 {{% hint style="info" %}}
 On Linux, `picocom` or `minicom` may be used instead of `screen`. The usb serial address might also be listed as `/dev/ttyUSB01` or a higher increment for `ttyUSB`. Additionally, the elevated permissions to access the device (e.g. group uucp/dialout or use `sudo`) may be required.
-{{< /hint >}}
+{{% /hint %}}
 
 ## Windows
 

content/gettingstarted/programming/repl/telnet.md

@@ -43,4 +43,4 @@ A terminal emulator is needed to open a telnet connection from Windows; the easi
 
 {{% hint style="info" %}}
 When using a Pycom device with a personal, home or office WiFi access point, the telnet connection may still be used. In this instance, the user will need to determine the Pycom device's local IP address and substitute this for `192.168.4.1`, referred to in the earlier sections.
-{{< /hint >}}
+{{% /hint %}}

content/gettingstarted/programming/safeboot.md

@@ -40,7 +40,7 @@ If problems occur within the filesystem or you wish to factory reset your module
 
 {{% hint style="danger" %}}
 Be aware, resetting the flash filesystem will delete all files inside the internal device storage (not the SD card) and they cannot be recovered.
-{{< /hint >}}
+{{% /hint %}}
 
 ## Reset
 

content/gettingstarted/registration/README.md

@@ -15,5 +15,5 @@ Some of our devices require registration before you can utilise specific feature
 
 {{% hint style="info" %}}
 **Not all Pycom devices require activation**; most features work immediately out of the box!
-{{< /hint >}}
+{{% /hint %}}
 

content/gettingstarted/registration/_index.md

@@ -15,5 +15,5 @@ Some of our devices require registration before you can utilise specific feature
 
 {{% hint style="info" %}}
 **Not all Pycom devices require activation**; most features work immediately out of the box!
-{{< /hint >}}
+{{% /hint %}}
 

content/gettingstarted/registration/lora/README.md

@@ -41,5 +41,5 @@ With ABP the encryption keys enabling communication with the network are preconf
 
 {{% hint style="info" %}}
 If you cannot find your favourite LoRaWAN network in the list above, please consider writing a tutorial for how to connect a Pycom module with it and contribute it to this documentation via a [GitHub pull request](https://github.com/pycom/pycom-documentation).
-{{< /hint >}}
+{{% /hint %}}
 

content/gettingstarted/registration/lora/_index.md

@@ -43,4 +43,4 @@ With ABP the encryption keys enabling communication with the network are preconf
 
 {{% hint style="info" %}}
 If you cannot find your favourite LoRaWAN network in the list above, please consider writing a tutorial for how to connect a Pycom module with it and contribute it to this documentation via a [GitHub pull request](https://github.com/pycom/pycom-documentation).
-{{< /hint >}}
+{{% /hint %}}

content/gettingstarted/registration/sigfox.md

@@ -18,7 +18,7 @@ Sigfox Pac is one-time activation code, which will be invalidated after device's
 Keep in mind that firmware updater will always display the same (even invalid) Sigfox Pac.
 In case of successive registration to a new account (or device type) on Sigfox Backend, you need to get Sigfox Pac from device page on Sigfox Backend.
 See [Sigfox documentation](https://support.sigfox.com/docs/device-idpac-couple) for more info.
-{{< /hint >}}
+{{% /hint %}}
 
 After first firmware update you can also get your _Sigfox ID_ and _Sigfox PAC_ through a couple of commands via the REPL.
 
@@ -53,7 +53,7 @@ Then provide the required information including email address and complete regis
 
 {{% hint style="info" %}}
 When registering your other devices (not your first device), you already have created Sigfox Account before. Be sure you are login with your Sigfox account. In that way all of your devices will be added to same Sigfox Account.
-{{< /hint >}}
+{{% /hint %}}
 
 ![](/gitbook/assets/sigfoxregistrationform.png)