Bug 1661434 - made content changes to some of the pages. r=sylvestre

Differential Revision: https://phabricator.services.mozilla.com/D88727

docs/contributing/debugging/debugging_on_mac_os_x.rst

@@ -1,12 +1,12 @@
 Debugging On Mac Os X
 =====================
 
-This document explains how to debug Mozilla-derived applications such as
+This document explains how to debug Gecko based applications such as
 Firefox, Thunderbird, and SeaMonkey on macOS using Xcode. If you want to
 debug from the terminal see :ref:`Debugging Mozilla with
 lldb <Debugging Firefox with LLDB>`. For specific
-information on a way to debug hangs, see `Debugging a hang on OS
-X <https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Debugging_a_hang_on_OS_X>`__.
+information on a way to debug hangs, see :ref:`Debugging a hang on OS
+X <Debugging A Hang On OS X>`.
 
 Creating a debuggable build
 ---------------------------
@@ -30,7 +30,6 @@ Official Builds
 ~~~~~~~~~~~~~~~
 
 At this time, official builds of Firefox 69 and later are Notarized.
-Uplifts to Firefox 68 and ESR 68 to enable Notarization are planned.
 **As a result, it is not possible to attach a debugger to these official
 Firefox releases on macOS 10.14+ without disabling System Integrity
 Protection (SIP).** This is due to Notarization requiring Hardened
@@ -43,8 +42,8 @@ try Server Builds
 ~~~~~~~~~~~~~~~~~
 
 In most cases, developers needing to debug a build as close as possible
-to the production environment should use a `try
-build <https://wiki.mozilla.org/ReleaseEngineering/TryServer>`__. These
+to the production environment should use a :ref:`try
+build <Try Server>`. These
 builds enable Hardened Runtime and only differ from production builds in
 that they are not Notarized which should not otherwise affect
 functionality, (other than the ability to easily launch the browser on
@@ -171,7 +170,7 @@ Setting up lldb
    not stop at them. If you don't include the Mozilla's .lldbinit, you
    must at least put
    ``settings set target.inline-breakpoint-strategy always`` in your
-   ``$HOME/.lldbinit`` as recommended on :ref:`Debugging Mozilla with
+   ``$HOME/.lldbinit`` as recommended on :ref:`Debugging Firefox with
    lldb <Debugging Firefox with LLDB>`.
 
 The
@@ -290,7 +289,7 @@ debugger will break there, and you will be able to debug it.
    ``$HOME/.lldbinit`` as recommended on :ref:`Debugging Mozilla with
    lldb <Debugging Firefox with LLDB>`.
 
-Using Mozilla-specific lldb commands
+Using Firefox-specific lldb commands
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you included the .lldbinit when `Setting up
@@ -346,6 +345,6 @@ techniques <https://developer.apple.com/library/mac/#technotes/tn2124/_index.htm
 Questions? Problems?
 ~~~~~~~~~~~~~~~~~~~~
 
-Try asking in our IRC channels
-`#developers <irc://irc.mozilla.org/developers>`__ or
-`#macdev <irc://irc.mozilla.org/macdev>`__.
+Try asking in our Element channels
+`#developers <https://chat.mozilla.org/#/room/#developers:mozilla.org>`__ or
+`#macdev <https://chat.mozilla.org/#/room/#macdev:mozilla.org>`__.

docs/contributing/debugging/debugging_on_windows.rst

@@ -1,10 +1,10 @@
 Debugging On Windows
 ====================
 
-This document explains how to debug Mozilla-derived applications such as
+This document explains how to debug Gecko based applications such as
 Firefox, Thunderbird, and SeaMonkey on Windows using the Visual C++ IDE.
 
-If VC++ and your Mozilla application hang shortly after you launch the
+If VC++ and your Gecko application hang shortly after you launch the
 application under the debugger, see `Problems Loading Debug
 Symbols <#problems-loading-debug-symbols>`__.
 
@@ -62,8 +62,7 @@ server <https://developer.mozilla.org/en-US/docs/Mozilla/Using_the_Mozilla_sourc
 Creating a Visual C++ project for Firefox
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Please refer to the documentation on
-:ref:`firefox-source-docs <Visual Studio Projects>`.
+Please refer to :ref:`this <Visual Studio Projects>`.
 
 Changing/setting the executable to debug
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -429,10 +428,8 @@ Got a tip?
 ~~~~~~~~~~
 
 If you think you know a cool Mozilla debugging trick, feel free to
-discuss it with `#developers <irc://irc.mozilla.org/developers>`__ and
+discuss it with `#developers <https://chat.mozilla.org/#/room/#developers:mozilla.org>`__ and
 then post it here.
 
-Originally by Heikki Toivonen.
-
 .. |Screenshot of disabling assertions| image:: /@api/deki/files/420/=Win32-debug-nop.png
    :class: internal

taskcluster/docs/task-graph.rst

@@ -24,8 +24,8 @@ work?
 
 All of this is controlled from within the Gecko source code, through a
 process called *task-graph generation*.  This means it's easy to add a
-new job or tweak the parameters of a job in a `try
-push <https://wiki.mozilla.org/Build:TryServer>`__, eventually landing
+new job or tweak the parameters of a job in a :ref:`try
+push <Try Server>`, eventually landing
 that change on an integration branch.
 
 The details of task-graph generation are documented :ref:`in the source