Replace IRC with matrix (#562)

* Replace IRC with matrix

* Update links

* Update links

_includes/connect.html

@@ -13,7 +13,7 @@ <h4>Twitter</h4>
         <div class="cell small-12 large-4">
             <h4>More</h4>
             <p><a href="https://t.me/addonschat" class="telegram">Telegram group</a></p>
-            <p><a href="https://wiki.mozilla.org/IRC" class="irc">IRC</a></p>
+            <p><a href="https://wiki.mozilla.org/Matrix" class="irc">Matrix</a></p>
             <p><a href="https://mail.mozilla.org/listinfo/dev-addons" class="mailinglist">Add-on Developers Mailing List</a></p>
         </div>
         <div class="cell small-12 large-5">

documentation/develop/comparison-with-xul-xpcom-extensions.md

@@ -143,7 +143,7 @@ The equivalent WebExtension scripts are called [background script](https://devel
 
 There are vastly more APIs available to XUL/XPCOM extensions than are available to WebExtensions, and for many XUL/XPCOM APIs, there isn't a WebExtensions substitute. The table below lists every API in the popular [Services.jsm](https://developer.mozilla.org/docs/Mozilla/JavaScript_code_modules/Services.jsm) module, describe what the equivalent WebExtensions API would be, if there is one.
 
-You'll see that many APIs have no WebExtensions equivalent yet. However, we are intending to extend the WebExtension APIs to support the needs of add-on developers, so if you have ideas, we'd love to hear them. You can reach us on the [dev-addons mailing list](https://mail.mozilla.org/listinfo/dev-addons) or [#webextensions](irc://irc.mozilla.org/webextensions) on [IRC](https://wiki.mozilla.org/IRC).
+You'll see that many APIs have no WebExtensions equivalent yet. However, we are intending to extend the WebExtension APIs to support the needs of add-on developers, so if you have ideas, we'd love to hear them. You can reach us on the [dev-addons mailing list](https://mail.mozilla.org/listinfo/dev-addons) or [Add-ons](https://mzl.la/2u8ZGbg) channel on [Matrix](https://wiki.mozilla.org/Matrix).
 
 {% capture table %}
 

documentation/develop/porting-a-google-chrome-extension.md

@@ -46,7 +46,7 @@ The browser extension APIs are designed to promote cross-browser compatibility a
 1. Review your use of `manifest.json` features and Chrome extension APIs against the [Chrome incompatibilities reference](https://developer.mozilla.org/Add-ons/WebExtensions/Chrome_incompatibilities). Mozilla provides a service that can help to automate this step: [extensiontest.com](https://www.extensiontest.com/). If you're using features or APIs that aren't supported in Firefox, you might not be able to port your extension.
 2. Install your extension in Firefox by using [about:debugging](https://developer.mozilla.org/docs/Tools/about:debugging) or the [web-ext tool](/documentation/develop/getting-started-with-web-ext#testing-out-an-extension) (similar to Chrome’s command-line tools).
 3. [Test your extension](/documentation/develop/debugging).
-4. If you have any problems, contact us on the [dev-addons mailing list](https://mail.mozilla.org/listinfo/dev-addons) or [#webextensions](irc://irc.mozilla.org/webextensions) on [IRC](https://wiki.mozilla.org/IRC).
+4. If you have any problems, contact us on the [dev-addons mailing list](https://mail.mozilla.org/listinfo/dev-addons) or [Add-ons](https://mzl.la/2u8ZGbg) channel on [Matrix](https://wiki.mozilla.org/Matrix).
 5. Package your extension, [manually](/documentation/publish/package-your-extension) or using the [web-ext](/documentation/develop/getting-started-with-web-ext#packaging-your-extension) tool.
 6. [Create an account on addons.mozilla.org then submit your add-on for signing and distribution](/documentation/publish/submitting-an-add-on).