Docs: Fix broken URLs where possible.

The remaining broken links are to the tickets on the deprecated Phabricator.
Those URLs shall be updated after migrating the issues to TF-M GitHub mirror.

Signed-off-by: Anton Komlev <anton.komlev@arm.com>
Change-Id: I3e8715bd4affc6829785f622804fa1f89116dd41
diff --git a/docs/contributing/contributing_process.rst b/docs/contributing/contributing_process.rst
index b959868..fc35b3a 100644
--- a/docs/contributing/contributing_process.rst
+++ b/docs/contributing/contributing_process.rst
@@ -9,10 +9,8 @@
 
 - It is recommended to subscribe to `TF-M mailing list <mailing_list_>`_
   via `this page <https://lists.trustedfirmware.org/mailman3/lists/tf-m.lists.trustedfirmware.org>`_.
-- Refer to the `Roadmap
-  <https://developer.trustedfirmware.org/w/tf_m/planning>`_ or send a mail to
-  the `TF-M mailing list <mailing_list_>`_ to get the latest status and plan of
-  TF-M.
+- Refer to the :doc:`/roadmap` or send a mail to the `TF-M mailing list <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.
 - Follow guidelines below to prepare the patch:
diff --git a/docs/contributing/maintainers.rst b/docs/contributing/maintainers.rst
index 5b4c68d..2b27255 100644
--- a/docs/contributing/maintainers.rst
+++ b/docs/contributing/maintainers.rst
@@ -4,9 +4,7 @@
 listed below. An acknowledgement from these code owners is required before
 the maintainers merge a contribution.
 
-More details may be found in the `Project Maintenance Process
-<https://developer.trustedfirmware.org/w/collaboration/project-maintenance-process/>`_
-document.
+More details may be found in the `Project Maintenance Process`_ document.
 
 Maintainers
 ===========
@@ -201,4 +199,6 @@
 
 =============
 
+.. _Project Maintenance Process: https://trusted-firmware-docs.readthedocs.io/en/latest/generic_processes/project_maintenance_process.html
+
 *Copyright (c) 2017-2024, Arm Limited. All rights reserved.*
diff --git a/docs/design_docs/tfm_builtin_keys.rst b/docs/design_docs/tfm_builtin_keys.rst
index fb22ab9..0ea583d 100644
--- a/docs/design_docs/tfm_builtin_keys.rst
+++ b/docs/design_docs/tfm_builtin_keys.rst
@@ -260,7 +260,7 @@
 **********
 
 .. [1] PSA cryptoprocessor driver interface: \ https://github.com/Mbed-TLS/mbedtls/blob/development/docs/proposed/psa-driver-interface.md
-.. [2] Definition of psa_key_location_t type in the PSA spec: \ https://armmbed.github.io/mbed-crypto/html/api/keys/lifetimes.html#c.psa_key_location_t
+.. [2] Definition of psa_key_location_t type in the PSA spec: \ https://arm-software.github.io/psa-api/crypto/1.1/api/keys/lifetimes.html#c.psa_key_location_t
 .. [3] Interface for platform keys: \ https://github.com/ARM-software/psa-crypto-api/issues/550
 
 --------------
diff --git a/docs/getting_started/tfm_getting_started.rst b/docs/getting_started/tfm_getting_started.rst
index 5976589..31cbf0f 100644
--- a/docs/getting_started/tfm_getting_started.rst
+++ b/docs/getting_started/tfm_getting_started.rst
@@ -185,7 +185,7 @@
           This defect has been fixed since Arm compiler v6.18.
           See [SDCOMP-59788] in Armclang v6.18 `release note`__ for details.
 
-          .. __: https://developer.arm.com/-/media/Arm%20Developer%20Community/Downloads/Arm%20Compiler%20for%20Embedded/6-18/Release%20notes%20for%20Arm%20Compiler%20for%20Embedded%206.pdf
+          .. __: https://developer.arm.com/documentation/107814/6-18
 
     - GNU Arm compiler v7.3.1+
 
@@ -221,7 +221,7 @@
 
           .. group-tab:: Linux
 
-              - Download IAR build tools from `here <https://www.iar.com/iar-embedded-workbench/build-tools-for-linux/>`__.
+              - Download IAR build tools from `here <https://www.iar.com/products/architectures/arm/iar-embedded-workbench-for-arm>`__.
               - Add IAR Arm compiler into environment:
 
                 .. code-block:: bash
@@ -230,7 +230,7 @@
 
           .. group-tab:: Windows
 
-              - Download IAR build tools from `here <https://www.iar.com/iar-embedded-workbench/#!?architecture=Arm>`__.
+              - Download IAR build tools from `here <https://www.iar.com/products/architectures/arm/iar-embedded-workbench-for-arm>`__.
               - Add IAR Arm compiler into environment:
 
                 .. code-block:: bash
diff --git a/docs/platform/nxp/lpcxpresso55s69/README.rst b/docs/platform/nxp/lpcxpresso55s69/README.rst
index bd4f127..3d4428b 100644
--- a/docs/platform/nxp/lpcxpresso55s69/README.rst
+++ b/docs/platform/nxp/lpcxpresso55s69/README.rst
@@ -58,16 +58,16 @@
 ===============================
 
 For command line flashing it is recommended to use external Segger J-Link flasher or to
-update the LPC-Link 2 debugger on the development board with the firmware provided by Segger, 
+update the LPC-Link 2 debugger on the development board with the firmware provided by Segger,
 which makes the device behave as if there is an on-board J-Link debugger.
 
-For onboard J-Link debugger option please follow this step: 
+For onboard J-Link debugger option please follow this step:
 
 2.1.1 Update the LPC-Link 2 to Segger J-Link
 --------------------------------------------
 
 -  Install a recent version of the `J-Link Software and Documentation
-   Pack <https://www.segger.com/downloads/jlink#J-LinkSoftwareAndDocumentationPack>`__.
+   Pack <https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack>`__.
    Version **6.98b** was used with this guide.
 
 -  Update the on-board LPC-Link 2 to use the latest J-Link firmware,
@@ -160,13 +160,13 @@
 
 2.2 Flashing with PyOCD
 =======================
-PyOCD is an open source Python package for programming and debugging Arm Cortex-M microcontrollers using multiple supported types of USB debug probes. 
+PyOCD is an open source Python package for programming and debugging Arm Cortex-M microcontrollers using multiple supported types of USB debug probes.
 See: `PyOCD <https://pypi.org/project/pyocd/>`__
 
 To flash TF-M images with PyOCD you can use the flash scripts provided in ``platform/ext/target/nxp/lpcxpresso55s69/scripts`` folder:
     - ``flash_PyOCD.py`` - for uploading image without BL2
     - ``flash_bl2_PyOCD.py`` - for uploading image with BL2
-    
+
 You should get the following output (flashing without BL2):
 ::
 
@@ -349,4 +349,4 @@
 *Copyright (c) 2020, Linaro. All rights reserved.*
 *Copyright (c) 2020-2021, Arm Limited. All rights reserved.*
 *Copyright 2020-2023 NXP. All rights reserved.
-*SPDX-License-Identifier: BSD-3-Clause*
\ No newline at end of file
+*SPDX-License-Identifier: BSD-3-Clause*
diff --git a/docs/security/index.rst b/docs/security/index.rst
index a51dacb..16ebe62 100644
--- a/docs/security/index.rst
+++ b/docs/security/index.rst
@@ -27,7 +27,7 @@
 .. warning::
    If any security vulnerability was found, please **do not**
    report it in the `issue tracker`_ or on the `mailing list`_. Instead, please
-   follow the `TrustedFirmware.org security incident process`_.
+   follow the `Security incident process`_.
 
 One of the goals of this process is to ensure providers of products that use
 TF-M have a chance to consider the implications of the vulnerability and its
@@ -44,10 +44,10 @@
 TF-M values researchers and community members who report vulnerabilities and
 TF-M policy is to credit the contributor's name in the published security advisory.
 
-.. _issue tracker: https://developer.trustedfirmware.org/project/view/2/
+.. _issue tracker: https://github.com/TrustedFirmware-M/trusted-firmware-m/issues
 .. _mailing list: https://lists.trustedfirmware.org/mailman3/lists/tf-m.lists.trustedfirmware.org/
-.. _TrustedFirmware.org security incident process: https://developer.trustedfirmware.org/w/collaboration/security_center/
-.. _Security Incident Process: https://developer.trustedfirmware.org/w/collaboration/security_center/reporting/
+.. _Security incident process: https://trusted-firmware-docs.readthedocs.io/en/latest/security_center/incident_handling_process.html
+
 
 --------------
 
diff --git a/docs/security/security_advisories/profile_small_key_id_encoding_vulnerability.rst b/docs/security/security_advisories/profile_small_key_id_encoding_vulnerability.rst
index 993f1a8..1f1c8cc 100644
--- a/docs/security/security_advisories/profile_small_key_id_encoding_vulnerability.rst
+++ b/docs/security/security_advisories/profile_small_key_id_encoding_vulnerability.rst
@@ -160,8 +160,7 @@
 `v1.4.1`_ fixed this issue as a patch release.
 
 .. _42e77b: https://review.trustedfirmware.org/plugins/gitiles/TF-M/trusted-firmware-m/+/42e77b561fcfe19819ff1e63cb7c0b672ee8ba41
-
-.. _v1.4.1: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tag/?h=TF-Mv1.4.1
+.. _v1.4.1: https://review.trustedfirmware.org/plugins/gitiles/TF-M/trusted-firmware-m/+/dd1fe44448db0f1750794cd9cf5596033f90f6f9
 
 ---------------------