Really dirty

iriark01 · iriark01 · commit eb82ae9da15c · 2020-02-20T13:42:25.000Z
diff --git a/docs/api/light-control.md b/docs/api/light-control.md
@@ -1,4 +1,4 @@
-<h2 id="light-control">Light control tutorial</h2>
+<h1 id="light-control">Light control tutorial</h1>
 
 The application below demonstrates a simple light control application, where devices can control the LED status of all devices in the network. You can build the application for the unsecure 6LoWPAN-ND or Thread network.
 
diff --git a/docs/api/lorawan/loraradio.md b/docs/api/lorawan/loraradio.md
@@ -1,4 +1,4 @@
-<h2 id="loraradio-api">LoRa radio driver</h2>
+<h1 id="loraradio-api">LoRa radio driver</h1>
 
 `LoRaRadio` is a pure virtual class that defines APIs for a LoRa radio driver.
 
diff --git a/docs/api/networkinterfaces/CellularInterface.md b/docs/api/networkinterfaces/CellularInterface.md
@@ -1,4 +1,4 @@
-<h2 id="cellular-api">Cellular API</h2>
+<h1 id="cellular-api">Cellular API</h1>
 
 <span class="images">![](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_interface.png)<span>CellularInterface class hierarchy</span></span>
 
diff --git a/docs/api/networkinterfaces/MeshInterface.md b/docs/api/networkinterfaces/MeshInterface.md
@@ -1,4 +1,4 @@
-<h2 id="mesh-api">Mesh</h2>
+<h1 id="mesh-api">Mesh</h1>
 
 <span class="images">![](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_mesh_interface.png)<span>MeshInterface class hierarchy</span></span>
 
diff --git a/docs/api/networkinterfaces/NetworkStatus.md b/docs/api/networkinterfaces/NetworkStatus.md
@@ -1,4 +1,4 @@
-<h2 id="network-status">Network status</h2>
+<h1 id="network-status">Network status</h1>
 
 This interface informs you about connection state changes asynchronously. Providing a method to register a callback function to a socket accomplishes this. Each time the network interface's state changes, it triggers the callback.
 
diff --git a/docs/api/networkinterfaces/ethernet-arch.md b/docs/api/networkinterfaces/ethernet-arch.md
@@ -1,4 +1,4 @@
-<h2 id="ethernet-technology">Ethernet</h2>
+<h1 id="ethernet-technology">Ethernet</h1>
 
 The term **Ethernet** refers to technologies first introduced in 1980 and standardized in 1983 as **IEEE 802.3**. Ethernet is a wired network, usually implemented by twisted pair wiring, or optical fiber and coaxials. However, coaxial has largely become obsolete.
 
diff --git a/docs/api/networkinterfaces/mesh-arch/6lowpan_nd_intro.md b/docs/api/networkinterfaces/mesh-arch/6lowpan_nd_intro.md
@@ -1,4 +1,4 @@
-<h2 id="6LoWPAN-ND-tech">6LoWPAN-ND</h2>
+<h1 id="6LoWPAN-ND-tech">6LoWPAN-ND</h1>
 
 6LoWPAN-ND (IPv6 over Low-Power Wireless Personal Area Networks with Neighbor Discovery) is a mesh protocol that loosely follows the [Zigbee-IP](https://www.zigbee.org/) specification. 6LoWPAN-ND allows IP-based networking to all nodes in the network.
 
diff --git a/docs/api/networkinterfaces/mesh-arch/thread_commissioning.md b/docs/api/networkinterfaces/mesh-arch/thread_commissioning.md
@@ -1,4 +1,4 @@
-<h2 id="thread-commissioning">How to commission a Thread device in practice</h2>
+<h1 id="thread-commissioning">How to commission a Thread device in practice</h1>
 
 ## Requirements
 
diff --git a/docs/api/networkinterfaces/mesh-arch/wisun_intro.md b/docs/api/networkinterfaces/mesh-arch/wisun_intro.md
@@ -1,4 +1,4 @@
-<h2 id="wisun-tech">Wi-SUN</h2>
+<h1 id="wisun-tech">Wi-SUN</h1>
 
 The Wi-SUN Field Area Network (FAN) is based on open standards from IEEE802, IETF, ANSI/TIA and ETSI.
 
diff --git a/docs/api/networkinterfaces/wifi-arch.md b/docs/api/networkinterfaces/wifi-arch.md
@@ -1,4 +1,4 @@
-<h2 id="wlan-technology">Wireless LAN</h2>
+<h1 id="wlan-technology">Wireless LAN</h1>
 
 One of the most popular connectivity technologies is Wireless LAN (Wireless Fidelity - Wi-Fi) as standardized in IEEE 802.11. It extends the Ethernet standards by making Ethernet wireless and adding required security.
 
diff --git a/docs/api/networksocket/networksocket.md b/docs/api/networksocket/networksocket.md
@@ -1,4 +1,4 @@
-<h2 id="network-socket">Network socket overview</h2>
+<h1 id="network-socket">Network socket overview</h1>
 
 The application programming interface for IP networking is the Socket API. As described in the [IP networking](../reference/ip-networking.html) section, the Socket API relates to OSI layer 4, the Transport layer. In Mbed OS, the Socket API is abstract and supports various protocols such as TCP, UDP and non-IP data delivery for NB-IoT cellular networks.
 
diff --git a/docs/api/platform/Error.md b/docs/api/platform/Error.md
@@ -1,4 +1,4 @@
-<h2 id="error-handling">Error handling</h2>
+<h1 id="error-handling">Error handling</h1>
 
 Mbed OS provides error status definitions and APIs for error construction, reporting and retrieving previously reported errors. Mbed OS also provides functions and macros to generate and define new error status values, extract information from error status values and to report errors into the system. Any software layer, such as applications, drivers, HAL and protocol stacks, can use these error handling APIs. The error functions also facilitate emitting an error message through STDOUT. `mbed_error.h` declares the error functions that Mbed OS provides.
 
diff --git a/docs/api/rtos/rtos.md b/docs/api/rtos/rtos.md
@@ -1,4 +1,4 @@
-<h2 id="rtos-api">RTOS overview</h2>
+<h1 id="rtos-api">RTOS overview</h1>
 
 The Mbed OS RTOS capabilities include managing objects such as threads, synchronization objects and timers. It also provides interfaces for attaching an application-specific idle hook function, reads the OS tick count and implements functionality to report RTOS errors.
 
diff --git a/docs/api/security/security.md b/docs/api/security/security.md
@@ -1,4 +1,4 @@
-<h2 id="psa-api">The Mbed implementation of PSA</h2>
+<h1 id="psa-api">The Mbed implementation of PSA</h1>
 
 The Mbed implementation of the Platform Security Architecture (PSA) provides root of trust services and infrastructure for developing IoT applications.
 
diff --git a/docs/api/storage/storage-arch.md b/docs/api/storage/storage-arch.md
@@ -1,4 +1,4 @@
-<h2 id="storage-tech">Architecture</h2>
+<h1 id="storage-tech">Architecture</h1>
 
 The architecture of the Mbed OS storage solution has the following properties:
 
diff --git a/docs/api/storage/storage-config.md b/docs/api/storage/storage-config.md
@@ -1,4 +1,4 @@
-<h2 id="storage-config">Configuration</h2>
+<h1 id="storage-config">Configuration</h1>
 
 This page describes the build-time configurable parameters for storage in Mbed OS:
 
diff --git a/docs/api/storage/storage.md b/docs/api/storage/storage.md
@@ -1,4 +1,4 @@
-<h2 id="storage-api">Storage overview</h2>
+<h1 id="storage-api">Storage overview</h1>
 
 The storage APIs present in Arm Mbed OS are:
 
diff --git a/docs/api/usb/usb_component.md b/docs/api/usb/usb_component.md
@@ -1,4 +1,4 @@
-<h2 id="usb-overview">USB components overview</h2>
+<h1 id="usb-overview">USB components overview</h1>
 
 The Universal Serial Bus (USB) is the most widely used bus in today's computer. USB has been designed to standardize connections between the computer and peripherals. For example, keyboards, mice, USB audio devices, printers, scanners, disk drives and cameras can use the same bus to exchange data with a computer.
 
diff --git a/docs/contributing/guidelines/ci.md b/docs/contributing/guidelines/ci.md
@@ -1,4 +1,4 @@
-<h2 id="ci">Continuous integration (CI) testing</h2>
+<h1 id="ci">Continuous integration (CI) testing</h1>
 
 Continuous integration (CI) testing is an integral part of the Mbed OS contribution workflow. CI testing refers mainly to automatic testing for pull requests.
 
diff --git a/docs/introduction/introduction.md b/docs/introduction/introduction.md
@@ -4,7 +4,7 @@ Mbed OS is an open-source operating system for platforms using Arm microcontroll
 
 <section class="row">
 <div class="columns large-6 medium-6 small-12">
-  <h2>On this page</h2>
+  <h2>On this page</h1>
   <ul class="guides-list">
           <ul data-tab-content>
                 <li><a href="#getting-started">Getting Started</a></li>
@@ -18,18 +18,18 @@ Mbed OS is an open-source operating system for platforms using Arm microcontroll
 </div>
 </section>
 
-<h2 id="getting-started">Getting started</h2>
+<h1 id="getting-started">Getting started</h1>
 
 If you want to dive straight in:
 
 - The source code is available on [GitHub](https://github.com/ARMmbed/mbed-os) and on our [release page](https://os.mbed.com/releases/).
 - Or [try our quick start](../quick-start/index.html).
 
-<h2 id="licensing">Source code and licensing</h2>
+<h1 id="licensing">Source code and licensing</h1>
 
 We release Mbed OS under an Apache 2.0 license, so you can confidently use it in commercial and personal projects. For more information about licensing, please see [our licensing documentation](../contributing/license.html).
 
-<h2 id="architecture">Architecture diagram</h2>
+<h1 id="architecture">Architecture diagram</h1>
 
 This is the basic architecture of an Mbed board:
 
@@ -77,15 +77,15 @@ Broadly speaking, the hardware you can see on our site is of three types:
 - **[Boards](https://os.mbed.com/platforms/)**: development boards are an inexpensive way to start developing with Mbed OS and other components.
 - **[Components](https://os.mbed.com/components/)**: the Component Database hosts reusable libraries for different hardware, middleware and IoT services that you can use with Arm Microcontrollers. These components can be used as building blocks for quickly developing prototypes and products.
 
-<h2 id="tools">Tools</h2>
+<h1 id="tools">Tools</h1>
 
 The Mbed product suite includes the tools you need to work with Mbed OS, whatever your skill level. If you are an experienced developer with a desktop setup, you may prefer working offline with Arm Mbed CLI, our Python-based command-line tool. You can use Mbed CLI with one of three supported toolchains: Arm Compiler 6, GCC and IAR. You can also [export projects](../tools/exporting.html) for other IDEs, such as Keil MDK. Mbed OS includes integration code for each supported toolchain to make it thread safe.
 
 If you prefer to work online, use the Arm Mbed Online Compiler, our online development tool, which lets you write and build applications using a web browser with no additional setup.
 
 You can use our debugging tools, DAPLink and pyOCD, to program and debug many devices. At the end of the development cycle, you can use the Mbed OS validation tools, Greentea and utest, to test your project.
 
-<h2 id="the-docs">The documentation</h2>
+<h1 id="the-docs">The documentation</h1>
 
 This is the technical documentation for Mbed OS. We have three types of documents: references, tutorials and porting guides. Our references are background technical material about our APIs, architecture and runtime execution. Our tutorials are step-by-step instructions that show you how to perform specific tasks and solve problems. Our porting guides show our silicon Partners how to port Mbed OS to their targets.
 
@@ -100,7 +100,7 @@ Please see the following sections of our documentation for more information.
 - [Contributing](../contributing/index.html), guidelines about contributing to our open-source project.
 - [Porting guides](../porting/index.html), for Partners and developers interested in porting targets to Mbed OS.
 
-<h2 id="docs-updates">Recently updated documentation</h2>
+<h1 id="docs-updates">Recently updated documentation</h1>
 
 - A guide to [porting a custom board](../porting/porting-a-custom-board.html).
 - A porting guide for the [static pin map extension](../porting/static-pinmap-port.html).
diff --git a/docs/migrating/MINAR_migration.md b/docs/migrating/MINAR_migration.md
@@ -1,4 +1,4 @@
-<h2 id="minar-migration">Migrating from MINAR (Arm Mbed OS 3)</h2>
+<h1 id="minar-migration">Migrating from MINAR (Arm Mbed OS 3)</h1>
 
 If you're looking to migrate your Arm Mbed application from Mbed OS 3 to Arm Mbed OS 5, one of the first things you're likely to notice is that [MINAR](https://github.com/ARMmbed/minar) (the event schduler in Mbed OS 3) does not exist in Mbed OS 5. This might be inconvenient, but there are different strategies that you can apply to port your Mbed OS 3 application to Mbed OS 5. This document presents some of these strategies from the MINAR perspective.
 
diff --git a/docs/migrating/migrate-from-mbed-os-2-to-5.md b/docs/migrating/migrate-from-mbed-os-2-to-5.md
@@ -169,6 +169,6 @@ Now, the program successfully compiles.
 
 Although the program or library now compiles successfully, runtime errors may still be present. Please visit the [compile-time errors tutorial](compile-time-errors.html#runtime-errors-and-lights-of-the-dead) for further debugging tips about common errors.
 
-<h2 id="enabling-bare-metal">Enabling Mbed OS bare metal</h2>
+<h1 id="enabling-bare-metal">Enabling Mbed OS bare metal</h1>
 
 Enabling the Mbed OS bare metal profile allows you to build Mbed OS without an RTOS. To enable it, you have to complete the [migration to Mbed OS 5](#migrating-to-mbed-os-5). Once the migration is complete, you can enable Mbed OS bare metal by following the instructions in the [bare metal example](../reference/bare-metal-example-application.html).
diff --git a/docs/program-setup/bare_metal/c_small_libs.md b/docs/program-setup/bare_metal/c_small_libs.md
@@ -1,4 +1,4 @@
-<h2 id="using-small-c-libraries">Using small C libraries in Mbed OS bare metal</h2>
+<h1 id="using-small-c-libraries">Using small C libraries in Mbed OS bare metal</h1>
 
 If your application does not use an RTOS, build it in the bare metal mode to achieve memory savings. Both the `ARM` and `GCC_ARM` toolchains support code optimized versions of their C standard libraries, `microlib` and `newlib-nano`. It is safe to use these smaller C libraries in bare metal mode, and we recommend using them.
 
diff --git a/docs/program-setup/runtime/Memory.md b/docs/program-setup/runtime/Memory.md
@@ -1,4 +1,4 @@
-<h2 id="memory-model">Memory</h2>
+<h1 id="memory-model">Memory</h1>
 
 This is a basic overview of the memory model in Mbed OS.
 
diff --git a/docs/program-setup/serial/serial_communication.md b/docs/program-setup/serial/serial_communication.md
@@ -1,4 +1,4 @@
-<h2 id="serial-comm">Board to PC communication over USB</h2>
+<h1 id="serial-comm">Board to PC communication over USB</h1>
 
 The Arm Mbed microcontroller on your board can communicate with a host PC over the same USB cable that you use for programming.
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="light-control">Light control tutorial</h2>`
	`1`	`+<h1 id="light-control">Light control tutorial</h1>`
`2`	`2`
`3`	`3`	`The application below demonstrates a simple light control application, where devices can control the LED status of all devices in the network. You can build the application for the unsecure 6LoWPAN-ND or Thread network.`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="loraradio-api">LoRa radio driver</h2>`
	`1`	`+<h1 id="loraradio-api">LoRa radio driver</h1>`
`2`	`2`
`3`	`3`	`LoRaRadio` is a pure virtual class that defines APIs for a LoRa radio driver.
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="cellular-api">Cellular API</h2>`
	`1`	`+<h1 id="cellular-api">Cellular API</h1>`
`2`	`2`
`3`	`3`	`<span class="images">![](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_cellular_interface.png)<span>CellularInterface class hierarchy</span></span>`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="mesh-api">Mesh</h2>`
	`1`	`+<h1 id="mesh-api">Mesh</h1>`
`2`	`2`
`3`	`3`	`<span class="images">![](https://os.mbed.com/docs/development/mbed-os-api-doxy/class_mesh_interface.png)<span>MeshInterface class hierarchy</span></span>`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="network-status">Network status</h2>`
	`1`	`+<h1 id="network-status">Network status</h1>`
`2`	`2`
`3`	`3`	`This interface informs you about connection state changes asynchronously. Providing a method to register a callback function to a socket accomplishes this. Each time the network interface's state changes, it triggers the callback.`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="ethernet-technology">Ethernet</h2>`
	`1`	`+<h1 id="ethernet-technology">Ethernet</h1>`
`2`	`2`
`3`	`3`	`The term Ethernet refers to technologies first introduced in 1980 and standardized in 1983 as IEEE 802.3. Ethernet is a wired network, usually implemented by twisted pair wiring, or optical fiber and coaxials. However, coaxial has largely become obsolete.`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="6LoWPAN-ND-tech">6LoWPAN-ND</h2>`
	`1`	`+<h1 id="6LoWPAN-ND-tech">6LoWPAN-ND</h1>`
`2`	`2`
`3`	`3`	`6LoWPAN-ND (IPv6 over Low-Power Wireless Personal Area Networks with Neighbor Discovery) is a mesh protocol that loosely follows the [Zigbee-IP](https://www.zigbee.org/) specification. 6LoWPAN-ND allows IP-based networking to all nodes in the network.`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="thread-commissioning">How to commission a Thread device in practice</h2>`
	`1`	`+<h1 id="thread-commissioning">How to commission a Thread device in practice</h1>`
`2`	`2`
`3`	`3`	`## Requirements`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="wisun-tech">Wi-SUN</h2>`
	`1`	`+<h1 id="wisun-tech">Wi-SUN</h1>`
`2`	`2`
`3`	`3`	`The Wi-SUN Field Area Network (FAN) is based on open standards from IEEE802, IETF, ANSI/TIA and ETSI.`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-<h2 id="wlan-technology">Wireless LAN</h2>`
	`1`	`+<h1 id="wlan-technology">Wireless LAN</h1>`
`2`	`2`
`3`	`3`	`One of the most popular connectivity technologies is Wireless LAN (Wireless Fidelity - Wi-Fi) as standardized in IEEE 802.11. It extends the Ethernet standards by making Ethernet wireless and adding required security.`
`4`	`4`