Update references to Mbed OS 6.7 from 6.5

Author: Donatien Garnier

check_tools/search_replace.json

@@ -3,5 +3,5 @@
     "replace": "https://github.com/ARMmbed/mbed-os-snippet-",
     "insert_start_tag": "https:\/\/github.com\/ARMmbed\/mbed-os-snippet-.*\/",
     "insert_end_tag": "\\)",
-    "insert_string": "tree/v6.5"
+    "insert_string": "tree/v6.7"
 }

docs/api/connectivity/bluetooth/Gap.md

@@ -73,4 +73,4 @@ The default value of data length supported by all controllers is 23 octets. If b
 
 Here is an example demonstrating how to use the GAP API to advertise, scan, connect and disconnect and how parameters influence efficiency of these actions.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GAP/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GAP/source/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GAP/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GAP/source/main.cpp)

docs/api/connectivity/bluetooth/GattClient.md

@@ -42,8 +42,8 @@ Clients register for these updates by setting the Client Characteristic Configur
 
 ### Characteristic writes
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattClient_CharacteristicWrite/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattClient_CharacteristicWrite/source/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattClient_CharacteristicWrite/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattClient_CharacteristicWrite/source/main.cpp)
 
 ### Characteristic updates
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattClient_CharacteristicUpdates/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattClient_CharacteristicUpdates/source/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattClient_CharacteristicUpdates/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattClient_CharacteristicUpdates/source/main.cpp)

docs/api/connectivity/bluetooth/GattServer.md

@@ -43,12 +43,12 @@ The term characteristic value update represents Characteristic Value Notificatio
 
 ### Add Service
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattServer_AddService/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattServer_AddService/source/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattServer_AddService/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattServer_AddService/source/main.cpp)
 
 ### Characteristic Writes
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattServer_CharacteristicWrite/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattServer_CharacteristicWrite/source/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattServer_CharacteristicWrite/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattServer_CharacteristicWrite/source/main.cpp)
 
 ### Characteristic Updates
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattServer_CharacteristicUpdates/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_GattServer_CharacteristicUpdates/source/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattServer_CharacteristicUpdates/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_GattServer_CharacteristicUpdates/source/main.cpp)

docs/api/connectivity/bluetooth/SecurityManager.md

@@ -52,4 +52,4 @@ The simplest example is a pairing of a device with no IO capabilities and no OOB
 
 The SecurityManager example demonstrates both a central and a peripheral connecting, performing basic pairing and setting up link security.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_SecurityAndPrivacy/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.5.0/BLE_SecurityAndPrivacy/source/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_SecurityAndPrivacy/source/)](https://github.com/ARMmbed/mbed-os-example-ble/blob/mbed-os-6.7.0/BLE_SecurityAndPrivacy/source/main.cpp)

docs/api/connectivity/lorawan/loraradio.md

@@ -12,7 +12,7 @@ To configure this class, please see the [LoRa configuration documentation](../ap
 
 ## LoRaRadio example
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-lorawan)](https://github.com/ARMmbed/mbed-os-example-lorawan/blob/mbed-os-6.5.0/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-lorawan)](https://github.com/ARMmbed/mbed-os-example-lorawan/blob/mbed-os-6.7.0/main.cpp)
 
 ## Related content
 

docs/api/connectivity/lorawan/lorawan.md

@@ -12,7 +12,7 @@ To configure this class, please see the [LoRa configuration documentation](../ap
 
 Please visit our Arm Mbed Online Compiler example, and follow the instructions in the `README.md`.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-lorawan)](https://github.com/ARMmbed/mbed-os-example-lorawan/blob/mbed-os-6.5.0/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-lorawan)](https://github.com/ARMmbed/mbed-os-example-lorawan/blob/mbed-os-6.7.0/main.cpp)
 
 ## Related content
 

docs/api/connectivity/networkinterfaces/CellularInterface.md

@@ -65,7 +65,7 @@ To bring up the network interface:
 
 This example establishes connection with the cellular network using Mbed OS CellularInterface.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-cellular)](https://github.com/ARMmbed/mbed-os-example-cellular/blob/mbed-os-6.5.0/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-cellular)](https://github.com/ARMmbed/mbed-os-example-cellular/blob/mbed-os-6.7.0/main.cpp)
 
 ## Related content
 

docs/api/connectivity/networkinterfaces/EthInterface.md

@@ -55,7 +55,7 @@ Network interface `connect` failure causes:
 
 Here is an example of an HTTP client program. The program brings up Ethernet as the underlying network interface and uses it to perform an HTTP transaction over a TCPSocket:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TCPSocket/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-TCPSocket/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TCPSocket/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-TCPSocket/blob/v6.7/main.cpp)
 
 ## Related content
 

docs/api/connectivity/networkinterfaces/MeshInterface.md

@@ -22,7 +22,7 @@ You can configure the mesh interface by providing values in `mbed_app.json`, as
 
 The following code snippet illustrates how you can use the MeshInterface API:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Mesh_Ex1/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-Mesh_Ex1/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Mesh_Ex1/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-Mesh_Ex1/blob/v6.7/main.cpp)
 
 
 ## Related content

docs/api/connectivity/networkinterfaces/NetworkStatus.md

@@ -113,7 +113,7 @@ This optional and has a small RAM and ROM increase, so applications are not requ
 
 Registering a status callback that connection state changes trigger depends on whether the network interface provides this functionality.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TCPSocket_ConnStateCb/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-TCPSocket_ConnStateCb/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TCPSocket_ConnStateCb/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-TCPSocket_ConnStateCb/blob/v6.7/main.cpp)
 
 ## Related content
 

docs/api/connectivity/networkinterfaces/WifiInterface.md

@@ -60,7 +60,7 @@ This program scans for Wi-Fi access points in the area. There are multiple [Wi-F
 
 The ESP8266Interface uses AT commands over serial interface to connect to an external Wi-Fi device. The OdinWiFiInterface provides an Ethernet-like driver to the Mbed OS network stack. The network stack uses the driver to connect to Wi-Fi:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TCPSocketWiFi/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-TCPSocketWiFi/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TCPSocketWiFi/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-TCPSocketWiFi/blob/v6.7/main.cpp)
 
 ## Related content
 

docs/api/connectivity/networksocket/CellularNonIPSocket.md

@@ -34,4 +34,4 @@ You can request Control Plane optimization mode either with CellularDevice's [`c
 
 The following code demonstrates how to create and use a cellular non-IP socket:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-CellularNonIPSocket/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-CellularNonIPSocket/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-CellularNonIPSocket/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-CellularNonIPSocket/blob/v6.7/main.cpp)

docs/api/connectivity/networksocket/DNS.md

@@ -44,7 +44,7 @@ Callback is called from thread context. If the callback takes more than 10ms to
 
 This DNS resolver example makes asynchronous DNS host name resolution.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-DNS_GetHostbyNameAsync/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-DNS_GetHostbyNameAsync/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-DNS_GetHostbyNameAsync/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-DNS_GetHostbyNameAsync/blob/v6.7/main.cpp)
 
 ## Troubleshooting information
 

docs/api/connectivity/networksocket/SocketAddress.md

@@ -10,7 +10,7 @@ Use the SocketAddress class to represent the IP address and port pair of a uniqu
 
 Here is an example to read current UTC time. This example uses the SocketAddress class to get the server IP address and port.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-UDPSocket/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-UDPSocket/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-UDPSocket/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-UDPSocket/blob/v6.7/main.cpp)
 
 ## Related content
 

docs/api/connectivity/networksocket/SocketStats.md

@@ -14,7 +14,7 @@ Socket statistics are stored in an internal data buffer and maintained for close
 
 Here is an example to collect socket statistics.
 
-[![View Example](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-socket-stats)](https://github.com/ARMmbed/mbed-os-example-socket-stats/blob/mbed-os-6.5.0/main.cpp)
+[![View Example](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-socket-stats)](https://github.com/ARMmbed/mbed-os-example-socket-stats/blob/mbed-os-6.7.0/main.cpp)
 
 ## Related content
 

docs/api/connectivity/networksocket/TCPSocket.md

@@ -26,7 +26,7 @@ Accepting a connection leaves the original socket in listening mode. You can con
 
 Here is a client example of HTTP transaction over TCPSocket:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TCPSocket/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-TCPSocket/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TCPSocket/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-TCPSocket/blob/v6.7/main.cpp)
 
 ## Related content
 

docs/api/connectivity/networksocket/UDPSocket.md

@@ -18,7 +18,7 @@ If you prefer to use `send()` and `recv()` functions and work only with one peer
 
 This UDP example reads the current UTC time by sending a request to the NIST Internet Time Service:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-UDPSocket/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-UDPSocket/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-UDPSocket/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-UDPSocket/blob/v6.7/main.cpp)
 
 ## Related content
 

docs/api/connectivity/networksocket/socket.md

@@ -32,7 +32,7 @@ Not all protocols implement every function from the Socket API. For example, UDP
 
 Here is a client example of HTTP transaction over TCPSocket:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-sockets)](https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.5.0/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-sockets)](https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.7.0/main.cpp)
 
 ## Related content
 

docs/api/connectivity/nfc/MessageBuilder.md

@@ -8,7 +8,7 @@ Mbed OS provides this API to construct NDEF messages, the common data format exc
 
 ## MessageBuilder example
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-MessageBuilder/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-MessageBuilder/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-MessageBuilder/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-MessageBuilder/blob/v6.7/main.cpp)
 
 ## Related content
 

docs/api/connectivity/nfc/NFCController.md

@@ -12,7 +12,7 @@ To use an NFC controller, you must initiate the instance with a driver instance,
 
 ## NFCController example
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-NFCController/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-NFCController/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-NFCController/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-NFCController/blob/v6.7/main.cpp)
 
 A delegate mechanism handles events throughout the API.
 

docs/api/connectivity/nfc/NFCEEPROM.md

@@ -12,7 +12,7 @@ To use an NFC EEPROM, you must initiate the instance with a driver instance, an
 
 ## NFCEEPROM example
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-NFC_EEPROM/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-NFC_EEPROM/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-NFC_EEPROM/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-NFC_EEPROM/blob/v6.7/main.cpp)
 
 ## Related content
 

docs/api/connectivity/nfc/SimpleMessageParser.md

@@ -10,7 +10,7 @@ The SimpleMessageParser class is a more integrated parser than the MessageParser
 
 ## SimpleMessageParser example
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-SimpleMessageParser/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-SimpleMessageParser/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-SimpleMessageParser/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-SimpleMessageParser/blob/v6.7/main.cpp)
 
 An application can extend capabilities of `SimpleMessageParser` by adding new record parsers (`mbed::nfc::ndef::RecordParser`) at runtime.
 

docs/api/connectivity/secure-socket/DTLSSocket.md

@@ -16,7 +16,7 @@ To use secure DTLS connections, application use the `DTLSSocketWrapper` through
 
 Please see the TLSSocket example:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.5.0/)](https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.5.0/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.7.0/)](https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.7.0/main.cpp)
 
 ## Related content
 

docs/api/connectivity/secure-socket/TLSSocket.md

@@ -14,7 +14,7 @@ To use secure TLS connections, the application uses the `TLSSocketWrapper` throu
 
 The TLSSocket example creates TLS connection to the HTTPS server and receives a simple response from the server:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.5.0/)](https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.5.0/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.7.0/)](https://github.com/ARMmbed/mbed-os-example-tls-socket/blob/mbed-os-6.7.0/main.cpp)
 
 ## Related content
 

docs/api/connectivity/tutorials/light-control.md

@@ -26,7 +26,7 @@ cd mbed-os-example-mesh-minimal
 
 If using the Mbed Online Compiler, click **Import into Mbed IDE** below:
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-mesh-minimal)](https://github.com/ARMmbed/mbed-os-example-mesh-minimal/blob/mbed-os-6.5.0/mesh_led_control_example.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-example-mesh-minimal)](https://github.com/ARMmbed/mbed-os-example-mesh-minimal/blob/mbed-os-6.7.0/mesh_led_control_example.cpp)
 
 ## Change the channel settings (optional)
 

docs/api/connectivity/tutorials/tls_tutorial.md

@@ -90,7 +90,7 @@ With everything in place, you can now set up a TLS socket connection. On the Mbe
 
 You set up a TLS socket in the same way as you set up a TCP socket, except you call `set_root_ca_cert` with the root CA string.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TLS_Communication/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-TLS_Communication/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-TLS_Communication/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-TLS_Communication/blob/v6.7/main.cpp)
 
 
 This now makes the request and returns the content of the file.

docs/api/connectivity/types/wifi-arch.md

@@ -17,8 +17,8 @@ The original version of the standard IEEE 802.11 was released in 1997. Updates a
 | 802.11a | 1999 | 6, 9, 12, 18, 24, 36, 48, 54 | 5.16 - 5.35 Ghz |
 | 802.11b | 1999 | 1, 2, 5.5, 11 | 2.401 - 2.495 Ghz |
 | 802.11g | 2003 | 1, 2, 5.5, 6, 9, 11, 12, 18, 24, 36, 48, 54 | 2.401 - 2.495 Ghz |
-| 802.11n | 2009 | 6.5 - 600 | Both 2.4 Ghz and 5 Ghz |
-| 802.11ac | 2013 | 6.5 - 1000 | 5 Ghz |
+| 802.11n | 2009 | 6.7 - 600 | Both 2.4 Ghz and 5 Ghz |
+| 802.11ac | 2013 | 6.7 - 1000 | 5 Ghz |
 
 Today, new access points and computers support all a/b/g/n/ac standards, and most embedded devices offer only a/b/g/n capability. The device and the access point negotiate speed and standard automatically without requiring a user configuration.git check.
 

docs/api/drivers/CAN.md

@@ -14,4 +14,4 @@ Controller-Area Network (CAN) is a bus standard that allows microcontrollers and
 
 This example sends a counter from one CAN bus (can1) and listens for a packet on the other CAN bus (can2). Each bus controller should be connected to a CAN bus transceiver. These should be connected together at a CAN bus.
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-CAN_ex_1/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-CAN_ex_1/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-CAN_ex_1/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-CAN_ex_1/blob/v6.7/main.cpp)

docs/api/drivers/I2C.md

@@ -16,4 +16,4 @@ The I2C protocol supports up to 127 devices per bus, and its default clock frequ
 
 ## I2C hello, world
 
-[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-I2C_ex_1/tree/v6.5)](https://github.com/ARMmbed/mbed-os-snippet-I2C_ex_1/blob/v6.5/main.cpp)
+[![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-I2C_ex_1/tree/v6.7)](https://github.com/ARMmbed/mbed-os-snippet-I2C_ex_1/blob/v6.7/main.cpp)