Update Fabric Synchronization Guide to avoid confusion (project-chip#34420)

* Update Fabric Synchronization Guide to avoid confusion

* Address the review comments

Author: yufengwangca

docs/guides/fabric_synchronization_guide.md

@@ -19,6 +19,9 @@ Fabric-Bridge-App example app implements the Aggregator device type with Fabric
 Synchronization condition met and demonstrates the end-to-end Fabric
 Synchronization feature using dynamic endpoints.
 
+The Fabric-Admin and Fabric-Bridge-App example applications must be executed on
+the same physical device and communicate with each other using RPC.
+
 Fabric Synchronization can be triggered from either side. The initiator of the
 Fabric Synchronization process, who shares their devices, takes on the
 Commissioner role. The recipient of the Fabric Synchronization request, who
@@ -82,11 +85,29 @@ fabricsync enable-auto-sync 1
 Pair the Fabric-Source bridge to Fabric-Sync with node ID 1:
 
 ```
-fabricsync add-bridge 1 <fabric-sink-ip>
+fabricsync add-bridge 1 <fabric-source-bridge-ip>
 ```
 
 ### Pair Light Example to Fabric-Source
 
+Since Fabric-Bridge also functions as a Matter server, running it alongside the
+Light Example app on the same machine would cause conflicts. Therefore, you need
+to run the Matter Light Example app on a separate physical machine from the one
+hosting Fabric-Admin and Fabric-Bridge. You can then commission the Matter Light
+Example app using Fabric-Admin on the source side.
+
+There is a workaround to avoid conflicts when running multiple Matter server
+applications on the same machine, you can use different ports and unique
+Key-Value Store (KVS) paths for each app. Here's an example of how to launch a
+Light App with custom settings:
+
+Light App with yet another set of different discriminator/passcode, ports and
+KVS
+
+```
+./out/linux-x64-light-clang/chip-lighting-app --discriminator 3843 --passcode 20202023 --secured-device-port 5543 --unsecured-commissioner-port 5553 --KVS /tmp/chip_kvs_lighting_app
+```
+
 Pair the Light Example with node ID 3 using its payload number:
 
 ```