DOCS: Replaces broken links

Replaces all links in the docs which have become outdated. This also
includes email addresses which are no longer active.

Change-Id: I6830237c311d2785efd78d5753b8393b1ba06234
Signed-off-by: Matthew Dalzell <matthew.dalzell@arm.com>
diff --git a/docs/contributing/contributing_process.rst b/docs/contributing/contributing_process.rst
index 25fb7dd..c17c22e 100644
--- a/docs/contributing/contributing_process.rst
+++ b/docs/contributing/contributing_process.rst
@@ -5,11 +5,12 @@
 
 .. Note::
 
-   Please contact `TF-M mailing list <mailing_list_>`_ for any question.
+   Please contact TF-M mailing list
+   `tf-m@lists.trustedfirmware.org <mailing_list_>`_ for any question.
 
-- It is recommended to subscribe to `TF-M mailing list <mailing_list_>`_
+- It is recommended to subscribe to TF-M mailing list
   via `this page <https://lists.trustedfirmware.org/mailman3/lists/tf-m.lists.trustedfirmware.org>`_.
-- Refer to the :doc:`/roadmap` or send a mail to the `TF-M mailing list <mailing_list_>`_
+- Refer to the :doc:`/roadmap` or send a mail to the TF-M mailing list `tf-m@lists.trustedfirmware.org <mailing_list_>`_
   to get the latest status and plan of TF-M.
 - Follow :doc:`Design Proposal Guideline </contributing/tfm_design_proposal_guideline>`
   to propose your design.
@@ -18,7 +19,7 @@
   - Clone the TF-M code on your own machine from `TF-M git repository
     <https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git>`_.
   - Follow the :doc:`TF-M getting started </getting_started/tfm_getting_started>`,
-    :doc:`Build Instructions </building/tfm_build_instruction>`
+    :doc:`Build Instructions </building/tfm_build_instruction>` and
     :doc:`Coding Guide </contributing/coding_guide>` for the TF-M project.
   - Make your changes in logical chunks to help reviewers. Each commit should
     be a separate review and either work properly or be squashed after the
@@ -68,7 +69,7 @@
   the patch.
 - You may be asked to provide further details or make additional changes.
 - You can discuss further with code owner(s) and maintainer(s) directly via
-  `TF-M mailing list <mailing_list_>`_ if necessary.
+  TF-M mailing list `tf-m@lists.trustedfirmware.org <mailing_list_>`_ if necessary.
 - If multiple patches are linked in a chain then code owners and maintainers
   should review and merge individual patches when they are ready, rather than
   waiting for the entire chain to be reviewed. If multiple patches are intended