From b4940fd8fa2cb177579f84d1902ea87995d0f16c Mon Sep 17 00:00:00 2001
From: gijsio <67470426+gijsio@users.noreply.github.com>
Date: Mon, 20 Jul 2020 13:59:31 +0200
Subject: [PATCH] some beautification

---
 content/_index.md                        |  3 ---
 content/firmwareapi/_index.md            |  7 +++----
 content/gettingstarted/_index.md         | 10 +++++-----
 content/tutorials/advanced/_index.md     |  6 ++++++
 content/tutorials/hardware/adc.md        |  3 ---
 content/tutorials/hardware/i2c.md        |  3 ---
 content/tutorials/hardware/owd.md        |  4 +---
 content/tutorials/networks/lte/_index.md |  7 +++++++
 themes/doc-theme/static/css/vuetify.css  |  2 +-
 9 files changed, 23 insertions(+), 22 deletions(-)
 create mode 100644 content/tutorials/advanced/_index.md

diff --git a/content/_index.md b/content/_index.md
index 033a604..6e78e0a 100644
--- a/content/_index.md
+++ b/content/_index.md
@@ -6,11 +6,8 @@ aliases:
 Pycom ecosystem makes IoT development easy
 
 * Choose [IoT hardware](products) which fit your project requirements.
-
 * Install Pymakr plugin in [Atom](https://atom.io/packages/pymakr) or [VS Code](https://marketplace.visualstudio.com/items?itemName=pycom.Pymakr) and start with your IoT project in seconds.
-
 * Write [MicroPython](https://micropython.org/) code and up to three times faster compared to C/C++.
-
 * Send data to [Pybytes IoT platform](https://pybytes.pycom.io/?utm_source=docs&utm_medium=web&utm_campaign=getting-started-top) or use your device standalone with the range of supported networks.
 * Start using our products [here!](/gettingstarted/)
 
diff --git a/content/firmwareapi/_index.md b/content/firmwareapi/_index.md
index 287d98a..7ac9f2c 100644
--- a/content/firmwareapi/_index.md
+++ b/content/firmwareapi/_index.md
@@ -8,10 +8,9 @@ aliases:
 
 This chapter describes modules (function and class libraries) that are built into MicroPython. There are a number of categories for the available modules:
 
-* Modules which implement a subset of standard Python functionality and are not intended to be extended by the user.
-* Modules which implement a subset of Python functionality, with a provision for extension by the user (via Python code).
-* Modules which implement MicroPython extensions to the Python standard libraries.
-* Modules specific to a particular port and thus not portable.
+* [implemented by Pycom](/firmwareapi/pycom/)
+* [Implemented by Micropython](/firmwareapi/micropython/)
+* External or custom modules and libraries
 
 ## Note about the availability of modules and their contents
 
diff --git a/content/gettingstarted/_index.md b/content/gettingstarted/_index.md
index 5a3c900..3fc126f 100644
--- a/content/gettingstarted/_index.md
+++ b/content/gettingstarted/_index.md
@@ -62,8 +62,8 @@ 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 %}}
+>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.
+
 
 4. Now that you have created a poject, we need to add some files. A standard MicroPython project will have a `lib` folder for additional libraries, and two python files: `main.py` and `boot.py`. 
 
@@ -140,11 +140,11 @@ Now that we got the basic example running, you can continue with the links below
 
 * [Get started using the FTP and Telnet Server](/gettingstarted/programming/ftp/)
 
-* [Connect using Pybytes](/pybytes/gettingstarted/)
+* [Connect using Pybytes](/pybytes/getstarted/)
 
-* [Registering with a network](/gettingstarted/network/)
+* [Registering with a network](/gettingstarted/registration/)
 
-* [Updating the firmware of your device](/firmwareupdate/)
+* [Updating the firmware of your device](/updatefirmware/)
 
 
 <!--## Step 4: (Optional) Connect through WiFi (Telnet & FTP)
diff --git a/content/tutorials/advanced/_index.md b/content/tutorials/advanced/_index.md
new file mode 100644
index 0000000..a0bd6e0
--- /dev/null
+++ b/content/tutorials/advanced/_index.md
@@ -0,0 +1,6 @@
+---
+title: "Advanced"
+aliases:
+    - chapter/tutorials/advanced
+---
+Under construction!
\ No newline at end of file
diff --git a/content/tutorials/hardware/adc.md b/content/tutorials/hardware/adc.md
index 8b76235..92cd75a 100644
--- a/content/tutorials/hardware/adc.md
+++ b/content/tutorials/hardware/adc.md
@@ -9,7 +9,6 @@ aliases:
 This example is a simple ADC sample. For more information please see [`ADC`](/firmwareapi/pycom/machine/adc).
 
 ```python
-
 from machine import ADC
 adc = ADC(0)
 adc_c = adc.channel(pin='P13')
@@ -22,7 +21,6 @@ adc_c.value()
 Currently the ESP32's ADC is not calibrated from the factory. This means it must be calibrated each time you wish to use it. To do this you must firstly measure the internal voltage reference. The following code will connect the 1.1v reference to `P22`
 
 ```python
-
 from machine import ADC
 adc = ADC()
 
@@ -33,7 +31,6 @@ adc.vref_to_pin('P22')
 Now that the voltage reference is externally accessible you should measure it with the most accurate voltmeter you have access to. Note down the reading in millivolts, e.g. `1120`. To disconnect the 1.1v reference from `P22` please reset your module. You can now calibrate the ADC by telling it the true value of the internal reference. You should then check your calibration by connecting the ADC to a known voltage source.
 
 ```python
-
 # Set calibration - see note above
 adc.vref(1100)
 
diff --git a/content/tutorials/hardware/i2c.md b/content/tutorials/hardware/i2c.md
index b545a2d..d203062 100644
--- a/content/tutorials/hardware/i2c.md
+++ b/content/tutorials/hardware/i2c.md
@@ -9,7 +9,6 @@ aliases:
 The following example receives data from a light sensor using I2C. Sensor used is the BH1750FVI Digital Light Sensor.
 
 ```python
-
 import time
 from machine import I2C
 import bh1750fvi
@@ -28,7 +27,6 @@ while(True):
 Place this sample code into a file named `bh1750fvi.py`. This can then be imported as a library.
 
 ```python
-
 # Simple driver for the BH1750FVI digital light sensor
 
 class BH1750FVI:
@@ -56,7 +54,6 @@ class BH1750FVI:
 This is the same code, with added LoRa connectivity, sending the lux value from the light sensor to another LoRa enabled device.
 
 ```python
-
 import socket
 import time
 import pycom
diff --git a/content/tutorials/hardware/owd.md b/content/tutorials/hardware/owd.md
index ab8c4b2..e39af80 100644
--- a/content/tutorials/hardware/owd.md
+++ b/content/tutorials/hardware/owd.md
@@ -10,8 +10,7 @@ This tutorial explains how to connect and read data from a DS18x20 temperature s
 
 ## Basic usage
 
-```python
-
+```
 import time
 from machine import Pin
 from onewire import DS18X20
@@ -31,7 +30,6 @@ while True:
 ## Library
 
 ```python
-
 #!/usr/bin/env python3
 
 """
diff --git a/content/tutorials/networks/lte/_index.md b/content/tutorials/networks/lte/_index.md
index 3a18f01..60f2ccd 100644
--- a/content/tutorials/networks/lte/_index.md
+++ b/content/tutorials/networks/lte/_index.md
@@ -21,3 +21,10 @@ while not lte.isattached()"
 print("LTE modem attached!")
 
 ```
+>Note: the first time, it can take a long while to attach to the network. 
+
+If you want to check the status of the modem while attaching, you can use the following commands:
+```python
+print(lte.send_at_cmd('AT!="showphy"')     # get the PHY status
+print(lte.send_at_cmd('AT!="fsm"')         # get the System FSM
+```
\ No newline at end of file
diff --git a/themes/doc-theme/static/css/vuetify.css b/themes/doc-theme/static/css/vuetify.css
index dfad456..64274ae 100644
--- a/themes/doc-theme/static/css/vuetify.css
+++ b/themes/doc-theme/static/css/vuetify.css
@@ -2755,7 +2755,7 @@ blockquote {
   font-size: 14px;
   font-weight: 300;
   background-color:rgba(0,128,0,0.7);
-  border-radius: 5px;
+  border-radius: 3px;
 }
 code,
 kbd {