Migrate term 'package' to 'extension' (#1280)

* Migrate term 'package' to 'extension'

* Bad link

* Add package term note

* Small article change

docs/SUMMARY.md

@@ -325,7 +325,7 @@
 
 ## #packages
 
-* [Packages](/packages)
+* [Extensions](/Extensions)
 
 ## #types
 

docs/about.md

@@ -90,10 +90,9 @@ When code is compiled to ARM machine code, the calls to JavaScript micro:bit fun
 
 Looking to use @homeurl@ in your favorite editor? Install the [command line tools](/cli) and get rolling!
 
-## [Packages](/packages)
+## [Extensions](/extensions)
 
-Create, edit and distribute your own blocks and JavaScript using [packages](/packages). Packages are hosted on GitHub and may be written
-using C++, JavaScript and/or ARM thumb.
+Create, edit and distribute your own blocks and JavaScript using [extensions](/extensions). Extensions are hosted on GitHub and may be written using C++, JavaScript and/or ARM thumb.
 
 ## [Open Source](/open-source)
 

docs/docs.md

@@ -28,6 +28,6 @@
 ## Developers
 
 * [Command Line Interface](/cli)
-* Learn about [packages](/packages)
+* Learn about [extensions](/extensions)
 * [Flashing via HID (CMSIS-DAP)](/hidflash)
 

docs/extensions.md

@@ -1,6 +1,6 @@
 # @extends
 
-## Package Gallery #gallery
+## Extension Gallery #gallery
 
 Check out [microbit.org](http://microbit.org/resellers/) for more information on these accessories and where to buy them.
 

docs/extensions/approval.md

@@ -4,7 +4,7 @@
 
 ## ~ hint
 
-All packages need approval by the Micro:bit Foundation before being available in the web editor. See:
+All extensions need approval by the Micro:bit Foundation before being available in the web editor. See:
 
 https://support.microbit.org/solution/articles/19000054952-package-approval
 

docs/extensions/build-your-own.md

@@ -0,0 +1,19 @@
+# Building your own extension
+
+In MakeCode you can create new custom blocks to use in the editor and include them in your projects. You do this by building an extension. Extensions are really useful for publishing drivers for accessories and hardware, as well as adding in new software features.
+
+Only extensions on the 'approved extension list' are available to users directly to add into the MakeCode editor at https://makecode.microbit.org.
+
+## Publishing extensions
+
+You publish an extension on GitHub and request **[approval](./approval)** for it if necessary.
+
+## How do I start building a extension?
+
+Go to the MakeCode extension documentation and see the [getting started](https://makecode.com/packages/getting-started) page.
+
+## ~ hint
+
+Extensions are also known, and referred to, as _packages_. The term _package_ is currently used in the MakeCode documentation for developing and deploying extensions.
+
+## ~

docs/open-source.md

@@ -13,8 +13,8 @@ The editor is open source on GitHub under the MIT license. Contributions are wel
 The [C++ micro:bit runtime](http://lancaster-university.github.io/microbit-docs/), created at [Lancaster University](http://www.lancaster.ac.uk/), provides access to the hardware functions of the micro:bit, 
 as well as a set of helper functions (such as displaying a number/image/string on the LED screen). 
 
-## Packages
+## Extensions
 
-* [microsoft/pxt-neopixel](https://github.com/microsoft/pxt-neopixel), package for neopixel strips
-* [microsoft/pxt-filesystem](https://github.com/microsoft/pxt-filesystem), package for the file system
-* [microsoft/pxt-max6675](https://github.com/microsoft/pxt-max6675), package for Temperature Probe (MAX6675)
+* [microsoft/pxt-neopixel](https://github.com/microsoft/pxt-neopixel), extension for neopixel strips
+* [microsoft/pxt-filesystem](https://github.com/microsoft/pxt-filesystem), extension for the file system
+* [microsoft/pxt-max6675](https://github.com/microsoft/pxt-max6675), extension for Temperature Probe (MAX6675)

docs/packages/build-your-own.md

@@ -1,13 +0,0 @@
-# Building your own package
-
-In MakeCode you can create new custom blocks to use in the editor and include them in your projects. You do this by building a package. Packages are really useful for publishing drivers for accessories and hardware, as well as adding in new software features.
-
-Only packages on the 'approved package list' are available to users directly to add into the MakeCode editor at https://makecode.microbit.org.
-
-## Publishing packages
-
-You publish a package on GitHub and request **[approval](./approval)** for it if necessary.
-
-## How do I start building a package?
-
-Go to the MakeCode package documentation and see the [getting started](https://makecode.com/packages/getting-started) page.

docs/projects/rc-car/code.md

@@ -1,15 +1,15 @@
 # Code
 
-## Step 1: Add the Kitronik package
+## Step 1: Add the Kitronik extension
 
-Kitronik has a package with blocks that program their motor driver. We need to add it to our project.
+Kitronik has an extension with blocks that program their motor driver. We need to add it to our project.
 
 * Click on **Advanced**
-* Click **Add Package**
+* Click **Extensions**
 * Type ``kitronik``, press **Enter**
-* Select the **kitronik-motor-driver** package
+* Select the **kitronik-motor-driver** extension
 
-After the package is loaded, you should see a new **Kitronik** category in the toolbox.
+After the extension is loaded, you should see a new **Kitronik** category in the toolbox.
 
 ## Step 2: Round and round we go!