Fix links in examples

Fix links that point to reorganized mbed-os-examples-docs_only, so the engine builds

Author: AnotherButler

docs/api/rtos/EventFlags.md

@@ -10,4 +10,4 @@ The EventFlags class provides a mechanism for setting and waiting for specific c
 
 ## EventFlags example
 
-[![View Example](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/EventFlags)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/EventFlags/main.cpp)
+[![View Example](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_RTOS/EventFlags)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_RTOS/EventFlags/main.cpp)

docs/api/rtos/EventQueue.md

@@ -61,7 +61,7 @@ To do this, set the `mbed_app.json` configuration option `events.shared-dispatch
 
 Use static EventQueue to prevent your program from failing due to queue memory exhaustion or to prevent dynamic memory allocation:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/events/static-event-queue/UserAllocatedEvent_ex_1/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/events/static-event-queue/UserAllocatedEvent_ex_1/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_RTOS/UserAllocatedEvent_ex_1)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_RTOS/UserAllocatedEvent_ex_1/main.cpp)
 
 ## Related content
 

docs/api/rtos/UserAllocatedEvent.md

@@ -21,8 +21,7 @@ The UserAllocatedEvent class is thread safe. The `call`, `try_call` and `cancel`
 
 This example demonstrates how you can instantiate, configure and post events:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/events/static-event-queue/UserAllocatedEvent_ex_1/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/events/static-event-queue/UserAllocatedEvent_ex_1/main.cpp)
-
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_RTOS/UserAllocatedEvent_ex_1)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_RTOS/UserAllocatedEvent_ex_1/main.cpp)
 
 ## Related content
 

docs/api/security/Devicekey.md

@@ -55,4 +55,4 @@ Run the DeviceKey functionality test with the `mbed` command as following:
 
 ## DeviceKey example
 
-[![View Example](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/DeviceKey)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/DeviceKey/main.cpp)
+[![View Example](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Security/DeviceKey)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Security/DeviceKey/main.cpp)

docs/api/storage/BlockDevice.md

@@ -42,7 +42,7 @@ For details regarding how to configure the default block device please refer to
 
 ## BlockDevice example
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/BlockDevice/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/BlockDevice/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/BlockDevice)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/BlockDevice/main.cpp)
 
 ## Related content
 

docs/api/storage/FlashIAPBlockDevice.md

@@ -17,7 +17,7 @@ To configure this class, please see our [BlockDevice configuration documentation
 
 ## FlashIAPBlockDevice example
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/FlashIAPBlockDevice/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/FlashIAPBlockDevice/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/FlashIAPBlockDevice)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/FlashIAPBlockDevice/main.cpp)
 
 ## Related content
 

docs/api/storage/MBRBlockDevice.md

@@ -19,11 +19,11 @@ You can view more information about the configurable settings and functions in t
 
 Partition a heap backed block device into two partitions. This example also uses the [HeapBlockDevice](heapblockdevice.html).
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/MBRBlockDevice/MBRBlockDevice_ex_1/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/MBRBlockDevice/MBRBlockDevice_ex_1/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/MBRBlockDevice_ex_1)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/MBRBlockDevice_ex_1/main.cpp)
 
 Partition an SD card, and format the new partition with a FAT filesystem. A PC will now be able to recognize the SD card.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/MBRBlockDevice/MBRBlockDevice_ex_2/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/MBRBlockDevice/MBRBlockDevice_ex_2/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/MBRBlockDevice_ex_2)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/MBRBlockDevice_ex_2/main.cpp)
 
 ## Related content
 

docs/api/storage/ProfilingBlockDevice.md

@@ -16,7 +16,7 @@ To configure this class, please see our [BlockDevice configuration documentation
 
 Create a ProfilingBlockDevice, perform storage operations and report back the read, write and erase counts.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/ProfilingBlockDevice/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/ProfilingBlockDevice/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/ProfilingBlockDevice)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/ProfilingBlockDevice/main.cpp)
 
 ## Related content
 

docs/api/storage/SDBlockDevice.md

@@ -76,7 +76,7 @@ There is a difference between `erase` as usually defined for SD cards and the de
 
 ## SDBlockDevice example application
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/SDBlockDevice)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/SDBlockDevice/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/SDBlockDevice)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/SDBlockDevice/main.cpp)
 
 ## Related content
 

docs/api/storage/SPIFBlockDevice.md

@@ -16,7 +16,7 @@ To configure this class, please see our [BlockDevice configuration documentation
 
 ## SPIFBlockDevice example
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/SPIFBlockDevice)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/SPIFBlockDevice/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/SPIFBlockDevice)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/SPIFBlockDevice/main.cpp)
 
 ## Related content
 

docs/api/storage/SlicingBlockDevice.md

@@ -20,7 +20,7 @@ To configure this class, please see our [BlockDevice configuration documentation
 
 This SlicingBlockDevice example partitions a [HeapBlockDevice](heapblockdevice.html) into three subunits and showcases programming and reading back data segments through both the underlying master block device and the sliced subunits.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/SlicingBlockDevice/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/blockdevices/SlicingBlockDevice/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/SlicingBlockDevice)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_Storage/SlicingBlockDevice/main.cpp)
 
 ## Related content
 

docs/api/usb/USBCDC_ECM.md

@@ -23,4 +23,4 @@ The example below sends an Ethernet frame that carries "Hello world" payload wit
 5. Click captured packet from source address 12:34:56:78:9a:bc to see the "Hello world" payload.
 
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/tree/master/USB/USBCDC_ECM)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/USB/USBCDC_ECM/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_USB/USBCDC_ECM)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_USB/USBCDC_ECM/main.cpp)

docs/porting/porting_full_process/porting.md

@@ -177,7 +177,7 @@ Detailed instructions for porting each module are given in the module-specific s
 
 The official `mbed-os-example-blinky` uses the RTOS, a DigitalOut object and timers. The bare metal version of the example doesn't rely on RTOS, GPIO and timers; LED toggling is done directly by accessing hardware registers. Modify the Blinky program you checked out earlier to not use the timer and DigitalOut object:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Direct-Register-Blinky/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Direct-Register-Blinky/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Porting_process/Direct-Register-Blinky)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Porting_process/Direct-Register-Blinky/main.cpp)
 
 ## Bootstrap and entry point
 
@@ -191,7 +191,7 @@ Mbed OS uses CMSIS for bootstrap. If your target doesn't have a CMSIS implementa
    C:\Keil_v5\ARM\PACK\ARM\CMSIS\5.3.0\Device\_Template_Vendor\Vendor\Device\Source
    C:\Keil_v5\ARM\PACK\ARM\CMSIS\5.3.0\Device\_Template_Vendor\Vendor\Device\Include
    ```
-   
+
 1. Create linker scripts from the templates.
 
 1. Implement pin mapping and basic peripheral initialization code.

docs/tutorials/using_apis/alarm-tutorial.md

@@ -15,7 +15,7 @@ cd mbed-os-example-alarm
 
 If using the Mbed Online Compiler, use the **Import into Mbed IDE" button below:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Alarm)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Alarm/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Alarm)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Alarm/main.cpp)
 
 ### Compile
 

docs/tutorials/using_apis/events_tutorial.md

@@ -158,4 +158,4 @@ This is only a small part of how event queues work in Mbed OS. The `EventQueue`,
 
 The EventQueue API provides a mechanism for creating a static queue, a queue that doesn't use any dynamic memory allocation and accepts only user-allocated events. After you create a static queue (by passing zero as `size` to its constructor), you can post `UserAllocatedEvent` to it. Using static EventQueue combined with UserAllocatedEvent ensures no dynamic memory allocation will take place during queue creation and events posting and dispatching. You can also declare queues and events as static objects (static in the C++ sense), and then memory for them will be reserved at compile time:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/events/static-event-queue/UserAllocatedEvent_ex_1/)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/events/static-event-queue/UserAllocatedEvent_ex_1/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_RTOS/UserAllocatedEvent_ex_1)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/APIs_RTOS/UserAllocatedEvent_ex_1/main.cpp)

docs/tutorials/using_apis/flow_control.md

@@ -14,7 +14,7 @@ If we want to automatically blink an LED, we have three main techniques:
 
 Busy wait is a method that blocks the processor for a period of time. This is an effective way to create time delays, but it’s inefficient because it wastes processor time and keeps the processor running at full power for the duration of the wait:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/tree/master/Flow-Control/Busy-Wait)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Flow-Control/Busy-Wait/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Busy-Wait)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Busy-Wait/main.cpp)
 
 Notice `printf()`; you can enable this by uncommenting the line (remove the `//`). `printf()` prints to the terminal, so you can use it to get debug information.
 
@@ -26,13 +26,13 @@ Tickers and timers are another way of creating a time interval. These methods ar
 
 Here is an example that doesn't include sleeping:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/tree/master/Flow-Control/Ticker)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Flow-Control/Ticker/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Ticker)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Ticker/main.cpp)
 
 ### Thread
 
 Threads are the most efficient way to blink an LED. During the waiting period, it is possible to take advantage of Mbed OS optimizations to automatically conserve power and deal with other tasks. While this is not the most visually appealing method, nor the simplest, it is the preferred way for large scale deployments:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/tree/master/Flow-Control/Thread)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Flow-Control/Thread/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Thread)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Thread/main.cpp)
 
 ## Flow control for manual actions
 
@@ -44,7 +44,7 @@ We can wait for digital input the same way we waited for time to pass - using a
 
 <span class="tips">**Tip:** You may need to change the `SW1` pin, as the button on your board may be called something else. Please refer to the pinmap on the [boards page](https://os.mbed.com/platforms/).</span>
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/tree/master/Flow-Control/Busy-Wait-Button)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Flow-Control/Busy-Wait-Button/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Busy-Wait-Button)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Busy-Wait-Button/main.cpp)
 
 We constantly poll the button to see whether it has a value that matches `button_press`. If it matches, we toggle the LED and wait 1 second.
 
@@ -54,7 +54,7 @@ We constantly poll the button to see whether it has a value that matches `button
 
 An alternative way to poll the button is to use an interrupt. Interrupts let you say `when that pin changes value, call this function`. In other words, we can tell the MCU to call a function when the button is pressed. In our case, that function toggles the LED:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/tree/master/Flow-Control/Interrupt-Button)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Flow-Control/Interrupt-Button/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Interrupt-Button)](https://github.com/ARMmbed/mbed-os-examples-docs_only/blob/master/Tutorials_UsingAPIs/Flow-Control-Interrupt-Button/main.cpp)
 
 In the code above a heartbeat function runs on LED2, which lets you see that your code is running. Then we connect an InterruptIn object to the button and set it so that when the button rises from 0 to 1, the toggle function is called; the function toggles LED1. This way we can turn the LED on and off as needed, without needing to “waste” our time waiting or actively polling an inactive button. We (or rather - the MCU) are free to move on to other things .