Generic docs update

docs/conf.py

@@ -112,7 +112,7 @@
     'css/custom.css',
 ]
 html_js_files = [
-    'https://kit.fontawesome.com/3102794088.js'
+    'https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/all.min.css'
 ]
 
 master_doc = 'index'

docs/examples/index.rst

@@ -92,58 +92,58 @@ Here is a list of all examples coming with this library.
 	Application needs to modify file ``/snippets/station_manager.c`` and update ``ap_list`` variable with preferred access points,
 	in order to allow *ESP* to connect to home/local network
 
-Access point
-************
+Ex. Access point
+****************
 
 *ESP* device is configured as software access point, allowing stations to connect to it.
 When station connects to access point, it will output its *MAC* and *IP* addresses.
 
-Client
-******
+Ex. Client
+**********
 
 Application tries to connect to custom server with classic, event-based API.
 It starts concurrent connections and processes data in its event callback function.
 
-Server
-******
+Ex. Server
+**********
 
 It starts server on port ``80`` in event based connection mode.
 Every client is processed in callback function.
 
 When *ESP* is successfully connected to access point, it is possible to connect to it using its assigned IP address.
 
-Domain name server
-******************
+Ex. Domain name server
+**********************
 
 *ESP* tries to get domain name from specific domain name, ``example.com`` as an example.
 It needs to be connected to access point to have access to global internet.
 
-MQTT Client
-***********
+Ex. MQTT Client
+***************
 
 This example demonstrates raw MQTT connection to mosquitto test server.
 A new application thread is started after *ESP* successfully connects to access point.
 MQTT application starts by initiating a new TCP connection.
 
 This is event-based example as there is no linear code.
 
-MQTT Client API
-***************
+Ex. MQTT Client API
+*******************
 
 Similar to *MQTT Client* examples, but it uses separate thread to process
 events in blocking mode. Application does not use events to process data,
 rather it uses blocking API to receive packets
 
-Netconn client
-**************
+Ex. Netconn client
+******************
 
 Netconn client is based on sequential API.
 It starts connection to server, sends initial request and then waits to receive data.
 
 Processing is in separate thread and fully sequential, no callbacks or events.
 
-Netconn server
-**************
+Ex. Netconn server
+******************
 
 Netconn server is based on sequential API.
 It starts server on specific port (see example details) and it waits for new client in separate threads.