Docs: Consistently refer to Musca-A

Updates documents to consistently refer to Musca-A, rather than using a
mix of Musca-A and Musca-A1.

Change-Id: I6f7a9e6afe3475b4a88200f6e56bf4c5507850e4
Signed-off-by: Jamie Fox <jamie.fox@arm.com>
diff --git a/docs/user_guides/tfm_build_instruction.rst b/docs/user_guides/tfm_build_instruction.rst
index 2b8c557..4097b71 100644
--- a/docs/user_guides/tfm_build_instruction.rst
+++ b/docs/user_guides/tfm_build_instruction.rst
@@ -29,7 +29,7 @@
             ``-DTARGET_PLATFORM=AN521``
           - Cortex-M23 IoT Kit subsystem for MPS2+ (AN519)
             ``-DTARGET_PLATFORM=AN519``
-          - Musca-A1 test chip board (Cortex-M33 SSE-200 subsystem)
+          - Musca-A test chip board (Cortex-M33 SSE-200 subsystem)
             ``-DTARGET_PLATFORM=MUSCA_A``
           - Musca-B1 test chip board (Cortex-M33 SSE-200 subsystem)
             ``-DTARGET_PLATFORM=MUSCA_B1``
diff --git a/docs/user_guides/tfm_integration_guide.rst b/docs/user_guides/tfm_integration_guide.rst
index 41f10ed..30e2771 100644
--- a/docs/user_guides/tfm_integration_guide.rst
+++ b/docs/user_guides/tfm_integration_guide.rst
@@ -21,7 +21,7 @@
 
 - Soft Macro Model (SMM) Cortex-M33 SSE-200 subsystem for MPS2+ (AN521)
 - Cortex-M23 IoT Kit subsystem for MPS2+ (AN519)
-- Musca-A1 test chip board (Cortex-M33 SSE-200 subsystem)
+- Musca-A test chip board (Cortex-M33 SSE-200 subsystem)
 - Musca-B1 test chip board (Cortex-M33 SSE-200 subsystem)
 
 The files related to the supported platforms are contained under the
@@ -33,7 +33,7 @@
 More information about subsystems supported by the MPS2+ board can be found in:
 `MPS2+ homepage <https://developer.arm.com/products/system-design/development-boards/fpga-prototyping-boards/mps2>`__
 
-More information about the Musca-A1 test chip board can be found in:
+More information about the Musca-A test chip board can be found in:
 `Musca-A homepage <https://developer.arm.com/products/system-design/development-boards/iot-test-chips-and-boards/musca-a-test-chip-board>`__
 
 More information about the Musca-B1 test chip board can be found in:
diff --git a/docs/user_guides/tfm_sw_requirement.rst b/docs/user_guides/tfm_sw_requirement.rst
index 0b2ee22..4ba3a19 100644
--- a/docs/user_guides/tfm_sw_requirement.rst
+++ b/docs/user_guides/tfm_sw_requirement.rst
@@ -264,8 +264,8 @@
 - pyyaml (pip3 install --user pyyaml)
 - jinja2 (pip3 install --user jinja2)
 - Python3 pip
-- `SRecord v1.63 <https://sourceforge.net/projects/srecord/>`__ (for
-  Musca-A1 test chip board)
+- `SRecord v1.63 <https://sourceforge.net/projects/srecord/>`__ (for Musca test
+  chip boards)
 
 Setup Cygwin to enable a compiler toolchain and CMake after installation.
 -------------------------------------------------------------------------
diff --git a/docs/user_guides/tfm_user_guide.rst b/docs/user_guides/tfm_user_guide.rst
index c7f9026..ec2bf9e 100644
--- a/docs/user_guides/tfm_user_guide.rst
+++ b/docs/user_guides/tfm_user_guide.rst
@@ -130,10 +130,10 @@
     [INF] Bootloader chainload address offset: 0x80000
     [INF] Jumping to the first image slot
     [Sec Thread] Secure image initializing!
-    
+
     #### Execute test suites for the secure storage service ####
     Running Test Suite SST secure interface tests (TFM_SST_TEST_2XXX)...
-    
+
     > Executing 'TFM_SST_TEST_2001'
       Description: 'Create interface'
       TEST PASSED!
@@ -186,10 +186,10 @@
 port (baud 115200 8n1) the following messages::
 
     [Sec Thread] Secure image initializing!
-    
+
     #### Execute test suites for the secure storage service ####
     Running Test Suite SST secure interface tests (TFM_SST_TEST_2XXX)...
-    
+
     > Executing 'TFM_SST_TEST_2001'
       Description: 'Create interface'
       TEST PASSED!
@@ -223,24 +223,24 @@
 #. Create a unified hex file comprising of both mcuboot and tfm_sign
    binary
 
--  For Musca-A1
+-  For Musca-A
 
    - Windows::
-   
+
       srec_cat.exe bl2\ext\mcuboot\mcuboot.bin -Binary -offset 0x200000 tfm_sign.bin -Binary -offset 0x220000 -o tfm.hex -Intel
-   
+
    - Linux::
-   
+
       srec_cat bl2/ext/mcuboot/mcuboot.bin -Binary -offset 0x200000 tfm_sign.bin -Binary -offset 0x220000 -o tfm.hex -Intel
 
 -  For Musca-B1
 
    - Windows::
-   
+
       srec_cat.exe bl2\ext\mcuboot\mcuboot.bin -Binary -offset 0xA000000 tfm_sign.bin -Binary -offset 0xA020000 -o tfm.hex -Intel
-   
+
    - Linux::
-   
+
       srec_cat bl2/ext/mcuboot/mcuboot.bin -Binary -offset 0xA000000 tfm_sign.bin -Binary -offset 0xA020000 -o tfm.hex -Intel
 
 #. Plug the Musca board into your computer. The board should appear as a USB
@@ -272,7 +272,7 @@
     [INF] Bootloader chainload address offset: 0x20000
     [INF] Jumping to the first image slot
     [Sec Thread] Secure image initializing!
-    
+
     #### Execute test suites for the secure storage service ####
     Running Test Suite SST secure interface tests (TFM_SST_TEST_2XXX)...
     > Executing 'TFM_SST_TEST_2001'