diff --git a/community/slack.md b/community/slack.md
index 99ae49b..62c7473 100644
--- a/community/slack.md
+++ b/community/slack.md
@@ -23,7 +23,7 @@ In addition to our regular [Micro:bit Educational Foundation newsletter](https:/
## Join us on the microbit-community slack channel!
-[Slack](https://slack) is a messaging service that allows teams and communities to connect online. It's a brilliant tool for live collaboration and the place to be for current micro:bit chatter!
+[Slack](https://slack.com) is a messaging service that allows teams and communities to connect online. It's a brilliant tool for live collaboration and the place to be for current micro:bit chatter!
Please note that Slack complements, but does not replace [micro:bit help & support](http://support.microbit.org, where you can search for help and ask the team questions.
diff --git a/hardware/1-5-revision.md b/hardware/1-5-revision.md
index ea5edf1..f065803 100644
--- a/hardware/1-5-revision.md
+++ b/hardware/1-5-revision.md
@@ -63,7 +63,7 @@ This allows the micro:bit to communicate with a wide range of Bluetooth devices,
| Channels | 50 2MHz channels, only 40 used (0 to 39), 3 advertising channels (37,38,39)
| Sensitivity | -93dBm in Bluetooth low energy mode
| Tx Power | -20dBM to 4dBm in 4 dB steps
-| Role | [GAP Peripheral](http://bluetooth-mdw.blogspot.co.uk/2016/07/microbit-and-bluetooth-roles.html)
+| Role | [GAP Peripheral](http://bluetooth-developer.blogspot.co.uk/2016/07/microbit-and-bluetooth-roles.html)
| Congestion avoidance | Adaptive Frequency Hopping
| Profiles | [BBC micro:bit profile](https://lancaster-university.github.io/microbit-docs/ble/profile/)
| More Info | [Bluetooth](../../bluetooth)
@@ -222,7 +222,7 @@ The interface processor can be used with special host tools to debug code that i
| --- | ---
| Protocol | CMSIS-DAP
| Options | JLink/OB (via different firmware)
-| More Info | [Mbed debugging micro:bit](https://os.mbed.com/docs/mbed-os/v5.11/tutorials/debug-microbit.html)
+| More Info | [Mbed debugging micro:bit](https://docs.mbed.com/docs/mbed-os-handbook/en/latest/debugging/debugging_microbit/)
### Mechanical
@@ -237,7 +237,7 @@ We have some [nice 2D and 3D CAD drawings and models of the micro:bit](https://g
- [BBC Technical Specifications](http://www.bbc.co.uk/mediacentre/mediapacks/microbit/specs)
-- [I2C specification](http://cache.nxp.com/documents/user_manual/UM10204.pdf)
+- [I2C specification](https://www.nxp.com/docs/en/user-guide/UM10204.pdf)
- [SPI 'specification'](https://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus)
diff --git a/latest-revision/assets/comparison-table.png b/latest-revision/assets/comparison-table.png
index 79e0d84..c8ee4da 100644
Binary files a/latest-revision/assets/comparison-table.png and b/latest-revision/assets/comparison-table.png differ
diff --git a/latest-revision/latest-revision-accessories.md b/latest-revision/latest-revision-accessories.md
index daab2d6..112b21f 100644
--- a/latest-revision/latest-revision-accessories.md
+++ b/latest-revision/latest-revision-accessories.md
@@ -104,6 +104,8 @@ If the extension is incompatible, the MakeCode editor will fail to compile the p
We are working behind the scenes on patching all MakeCode extensions that are currently incompatible. If we have not made contact or you wish to discuss any issues, please get in touch.
+A current list of extensions with issues can be found in https://github.com/microsoft/pxt-microbit/issues/3506
+
### Python modules
The additional memory available to the latest revision means that you have more space to create python modules to work with your accessories and the micro:bit.
@@ -117,7 +119,7 @@ The latest board revision introduces a superset of the Intel-Hex format that ena
A **Universal Hex** hex file will work on a v1 or V2 board.
A clear indication that you are working with this format is that a compiled .hex file will be ~1.8Mb as opposed to ~700Kb in size.
-A [Universal Hex JavaScript Library](https://github.com/microbit-foundation/microbit-universal-hex) has been written to implement the format and associated detailed [specification of the Universal Hex format](https://github.com/microbit-foundation/universal-hex/). Please [get in contact](mailto:support@microbit.org?subject=Request%20for%20access%20to%20Universal%20hex&20spec&body=Name%3A%0D%0A%0D%0AGitHub%20ID%3A) if you require access to the specification.
+A [Universal Hex JavaScript Library](https://github.com/microbit-foundation/microbit-universal-hex) has been written to implement the format and associated detailed specification of the Universal Hex format. Please [get in contact](mailto:support@microbit.org?subject=Request%20for%20access%20to%20Universal%20hex&20spec&body=Name%3A%0D%0A%0D%0AGitHub%20ID%3A) if you require access to the specification.
### Hex format compatibility
diff --git a/latest-revision/latest-revision-main.md b/latest-revision/latest-revision-main.md
index aa62014..d7e31fb 100644
--- a/latest-revision/latest-revision-main.md
+++ b/latest-revision/latest-revision-main.md
@@ -136,16 +136,10 @@ To access the features of the latest revision only (eg. to output sound only on
Features that are common to all board variants will work in the same way they always have. For example, you will be able to use the same blocks in MakeCode to use the acceleromater on any board revision.
-### MakeCode
-
### Makecode
-You can use the latest board revision in the beta editor [https://makecode.microbit.org/beta](https://makecode.microbit.org/beta) alongside the current revision. This editor does not yet have support for V2 features.
-
-#### Using the new features in MakeCode
-
-An alpha version of the MakeCode editor that includes the latest V2 feature blocks is available at [https://makecode.microbit.org/v3.1](https://makecode.microbit.org/v3.1)
+You can use the latest board revision in the beta editor [https://makecode.microbit.org/beta](https://makecode.microbit.org/beta) alongside the current revision.
-#### V2 MakeCode APIs
+#### Using the new features in MakeCode beta
The Microphone and Logo touch features can be found in the Input menu
diff --git a/software/micropython.md b/software/micropython.md
index 7bccb31..8647547 100644
--- a/software/micropython.md
+++ b/software/micropython.md
@@ -128,8 +128,6 @@ Tutorials and API documentation for developers can be [found here](https://micro
- [Log a new issue](https://github.com/bbcmicrobit/micropython/issues/new)
-- [Ask a question on the mailing list](https://mail.python.org/mailman/listinfo/microbit) (you must be a member of the mailing list before you can post to it).
-
### Source Code
- [MicroPython on the micro:bit source code](https://github.com/bbcmicrobit/micropython)
diff --git a/software/runtime.md b/software/runtime.md
index 25fb1a5..cc43962 100644
--- a/software/runtime.md
+++ b/software/runtime.md
@@ -107,4 +107,4 @@ Crucially, this includes Nordic's [Soft Device 110](https://www.nordicsemi.com/S
The SoftDevice runs on the same MCU as the user's code, and when using the Mbed BLE APIs (that the micro:bit runtime also uses), calls are made into SoftDevice. SoftDevice also occupies the highest priority interrupts, so that user code can be pre-empted by SoftDevice when this is required for the radio to function properly.
-v1 only. Micro:bit programs use SoftDevice S110 by default, which only allows the device to be a [GAP Peripheral](http://bluetooth-mdw.blogspot.co.uk/2016/07/microbit-and-bluetooth-roles.html). It is possible to use [Soft Device S130](https://www.nordicsemi.com/Software-and-tools/Software/S130) with the micro:bit by compiling offline with Mbed, though that is beyond the scope of this documentation.
+v1 only. Micro:bit programs use SoftDevice S110 by default, which only allows the device to be a [GAP Peripheral](http://bluetooth-developer.blogspot.co.uk/2016/07/microbit-and-bluetooth-roles.html). It is possible to use [Soft Device S130](https://www.nordicsemi.com/Software-and-tools/Software/S130) with the micro:bit by compiling offline with Mbed, though that is beyond the scope of this documentation.