Build: Restructure Musca-B1 folders

Original musca_b1 platform is renamed to musca_b1/sse_200, and
musca_b1_secure_enclave is renamed to musca_b1/secure_enclave.

Change-Id: If05f1878cff3808ec95e207abe4a0a433998523c
Signed-off-by: Gabor Abonyi <gabor.abonyi@arm.com>
Signed-off-by: Mark Horvath <mark.horvath@arm.com>
diff --git a/docs/getting_started/tfm_user_guide.rst b/docs/getting_started/tfm_user_guide.rst
index 58746ef..1a2de50 100644
--- a/docs/getting_started/tfm_user_guide.rst
+++ b/docs/getting_started/tfm_user_guide.rst
@@ -224,7 +224,7 @@
 .. Note::
 
     Before executing any images on Musca-B1 board, please check the
-    :doc:`target platform readme </platform/ext/target/musca_b1/readme>`
+    :doc:`target platform readme </platform/ext/target/musca_b1/sse_200/readme>`
     to have the correct setup.
 
 Example application with BL2 bootloader
@@ -431,7 +431,7 @@
 ============================================================================
 
 Follow the above procedures, but to create a unified hex please check the
-:doc:`Musca-B1 Secure Enclave readme </platform/ext/target/musca_b1_secure_enclave/readme>`.
+:doc:`Musca-B1 Secure Enclave readme </platform/ext/target/musca_b1/secure_enclave/readme>`.
 
 ********************************************************
 Execute TF-M example and regression tests on MPS3 boards