Merge pull request #4 from silabs-ArghyaD/review/matter-documentation

Matter documentation minor fixes

Author: silabs-vm

sld120-matter-wifi-getting-started/04-light-switch-step-by-step-example.md

@@ -21,7 +21,7 @@ This procedure prepares the Raspberry Pi 4B (RPi4B) to become a Matter Hub. You
 4. Use PuTTY to connect to RPi4B.
 
    1. The first time connecting to RPi4B, PuTTY will warn about a new host key or key fingerprint. Accept the key.
-   2. The credentials (username: password) are the same given Step 1.
+   2. The credentials (username: password) are the same as those given in Step 1.
    3. Switch to root mode and navigate to path "/home/ubuntu/connectedhomeip/out/standalone" to find the chip-tool.
 
 Matter hub/chip-tool are ready and working. Keep the PuTTY session open for the following steps.
@@ -92,8 +92,8 @@ Now two Matter accessory devices (MADs) are on the network and ready to be used.
 
 1. In a PuTTY session to the Matter hub, use the chip-tool to test the Matter light device.
 
-   1. Control the light status of the light MAD Using `./chip-tool onoff on nodeID 1`. You can also use `chip-tool onoff off` and `chip-tool toggle`.
-   2. For dev board with buttons available, you can use BTN1 to toggle the light status locally.
+   1. Control the light status of the light MAD using `./chip-tool onoff on nodeID 1`. You can also use `chip-tool onoff off` and `chip-tool toggle`.
+   2. For dev boards with buttons available, you can use BTN1 to toggle the light status locally.
 
 2. In a PuTTY session to the Matter hub, use the chip-tool to bind the light_switch MAD to the light MAD, thus allowing the switch to control the light.
 

sld120-matter-wifi-getting-started/07-next-steps-other-resources.md

@@ -1,6 +1,6 @@
 # Next Steps
 
-Now that you have gotten a sense of what goes into making a Matter network, you can begin to customize MADs and other features for your own purposes. The [Developers' Guide](/matter/{build-docspace-version}/matter-developers-guide-overview) contains more detail than was provided in this Quick-Start guide, and also contains information on a number of special development topics. Your Matter Extension package contains a number of other Matter examples that you can use as a starting point, the first two of which were used in this example.
+Now that you have gotten a sense of what goes into making a Matter network, you can begin to customize MADs and other features for your own purposes. The [Developers' Guide](/matter/{build-docspace-version}/matter-developers-guide-overview) contains more detail than was provided in this Quick-Start guide, and also contains information on a number of special development topics. Your Matter Extension package contains a number of other Matter examples that you can use as a starting point, the first two of which were used in this example:
 
 - Matter SoC Light over Wi-Fi
 

sld246-matter-faq/wifi-faq.md

@@ -184,7 +184,7 @@ When this happens, perform the following steps to run the OTA Update successfull
 
 1. Disconnect the WF200 Expansion Board from the EFR32MG24.
 
-2. Go To the Simplicity Commander's folder path in the command prompt and run this command:
+2. Go to the Simplicity Commander's folder path in the command prompt and run this command:
 
    ```shell
    commander.exe extflash read --range 0x00:+<total size to read>

sld247-matter-overview/index.md

@@ -77,7 +77,7 @@ Pre-built images for the SiWx917 connectivity firmware are available per the ins
 
 **Simplicity Commander**: [Simplicity Commander](/matter/{build-docspace-version}/matter-references/flash-silabs-device#simplicity-commander) is a utility that provides GUI and command line access to the debug features of an EFM32 device. It allows you to flash firmware, update the kit firmware, and lock or unlock debug access.
 
-**Tera Term**: [Tera Term](https://osdn.net/projects/ttssh2/releases/) is the terminal emulator for Microsoft Windows that supports serial port, telnet, and SSH connections.
+**Tera Term**: [Tera Term](https://github.com/TeraTermProject/osdn-download) is the terminal emulator for Microsoft Windows that supports serial port, telnet, and SSH connections.
 
 **Silicon Labs Matter SiSDK Extension**: Once Simplicity Studio 5 is installed, you will be prompted to install the Simplicity SDK, formerly released as Gecko SDK (GSDK). Here you should also install the Matter Enablement Package by making sure the extension is checked, as shown.
 

sld248-matter-overview-guides/code-size-savings.md

@@ -4,7 +4,7 @@ Silicon Labs' Matter example applications come out of the box with various ease-
 
 To reduce the total size of your application's image while still maintaining basic core Matter functionality, you can take a few steps:
 
-1. Remove optional components in from the Matter Project in Studio that may not be needed for a certain application. For example, removing the components Matter Display and Matter QR Code Display will save flash by disabling the LCD screen.
+1. Remove optional components from the Matter Project in Studio that may not be needed for a certain application. For example, removing the components Matter Display and Matter QR Code Display will save flash by disabling the LCD screen.
 2. Remove any excess printing from the application. In practice, this can include removing the Matter Shell component and RTT Logging from the Matter device.
 3. Install the `matter_no_debug` and/or `matter_no_lcd_shell` components. This will automatically take care of removing these extra features (`matter_no_lcd_shell`) as well as implement the defines and configuration values (`matter_no_debug`) to achieve optimal image size reduction at the click of a button.
 4. Remove clusters from the zap configuration. Example applications have clusters enabled to support both Thread and Wi-Fi transport layers such as the Diagnostics clusters. It is important to note that certain device types require different Matter Clusters. Be sure to check the [Matter Specifications](https://csa-iot.org/developer-resource/specifications-download-request/) to confirm which Matter Clusters are required for your device type.

sld248-matter-overview-guides/matter-icd.md

@@ -73,9 +73,9 @@ These configurations are independent from the underlying transport configuration
 These configurations can be changed by modifying the configuration of the `ICD Server Configuration` component or directly by setting values in `sl_matter_icd_config.h`.
 
 ```cpp
-    #define SL_IDLE_MODE_DURATION_S = 600     // 10min Idle Mode Interval
-    #define SL_ACTIVE_MODE_INTERVAL = 1000  // 1s Active Mode Interval
-    #define SL_ACTIVE_MODE_THRESHOLD = 500  // 500ms Active Mode Threshold
+    #define SL_IDLE_MODE_DURATION_S 600     // 10min Idle Mode Interval
+    #define SL_ACTIVE_MODE_INTERVAL 1000  // 1s Active Mode Interval
+    #define SL_ACTIVE_MODE_THRESHOLD 500  // 500ms Active Mode Threshold
 ```
 
 ### ICD Check-In Protocol Use-Case
@@ -305,9 +305,9 @@ The recommended configurations are likely to change with the Matter 1.4 release.
 Configuration parameters of the ICD Server Configuration component (sl_matter_icd_config.h):
 
 ```cpp
-    #define SL_IDLE_MODE_DURATION_S  = 600    // 10min Idle Mode Interval
-    #define SL_ACTIVE_MODE_INTERVAL  = 10000  // 10s Active Mode Interval
-    #define SL_ACTIVE_MODE_THRESHOLD = 1000   // 1s Active Mode Threshold
+    #define SL_IDLE_MODE_DURATION_S  600    // 10min Idle Mode Interval
+    #define SL_ACTIVE_MODE_INTERVAL  10000  // 10s Active Mode Interval
+    #define SL_ACTIVE_MODE_THRESHOLD 1000   // 1s Active Mode Threshold
 ```
 
 **Openthread Configuration flags**
@@ -370,9 +370,9 @@ The last three parameters are configuration parameters in the Matter Core Compon
 Configuration parameters of the ICD Server Configuration component (`sl_matter_icd_config.h`):
 
 ```cpp
-    #define SL_IDLE_MODE_DURATION_S  = 3600   // 60min Idle Mode Interval
-    #define SL_ACTIVE_MODE_INTERVAL  = 0      // 0s Active Mode Interval
-    #define SL_ACTIVE_MODE_THRESHOLD = 5000   // 5s Active Mode Threshold
+    #define SL_IDLE_MODE_DURATION_S  3600   // 60min Idle Mode Interval
+    #define SL_ACTIVE_MODE_INTERVAL  0      // 0s Active Mode Interval
+    #define SL_ACTIVE_MODE_THRESHOLD 5000   // 5s Active Mode Threshold
 ```
 
 **Openthread Configuration flags**

sld249-matter-prerequisites/hardware-requirements.md

@@ -112,7 +112,6 @@ The following boards are supported for the Matter over Wi-Fi demos and developme
     - WF200 / Single Band Wi-Fi Expansion Board / 2.4GHz
       - [SLEXP8023A](https://www.silabs.com/development-tools/wireless/wi-fi/wfm200-wifi-expansion-kit)
 - Interconnect board (included in the Wi-Fi kits)
-- Interconnect board (included in the Wi-Fi kits)
 - SPI Cable (included in the RS9116 kit)
 - Jumper Cables (included in the RS9116 kit)
 

sld249-matter-prerequisites/matter-artifacts.md

@@ -50,14 +50,16 @@ https://github.com/SiliconLabs/matter_extension/releases/download/v2.6.0/SiWx917
 
 **Note**:
 
-- SiWN917 NCP board need to be flashed with proper firmware as mentioned below:
+- SiWN917 NCP boards need to be flashed with proper firmware as mentioned below:
 
   - `SiWG917-B.2.x.X.X.X.rps - This firmware image is valid for BRD8045A (B0 Expansion v2.0) board`
 
 - SiWG917 SoC boards need to be flashed with proper firmware as mentioned below:
 
   - `SiWG917-B.2.x.X.X.X.rps - This firmware image is valid for BRD4338A(B0 common flash v2.0) board`
 
+[Both the points in the Note refer to the same file]: #
+
 ## Matter SiWx917 RCP Linux app and Configuration file
 
 The SiWx917 RCP folder (siwx917_rcp_files.zip) contains the Matter Linux all-cluster-app, which can be run on a Raspberry Pi, and the wfx-sdio-overlay.dts file, a Device Tree Source file used to configure the SDIO interface on the Raspberry Pi to detect and communicate with the SiWx917 RCP.

sld250-matter-references/custom-matter-device.md

@@ -120,7 +120,7 @@ $ mattertool levelcontrol move-to-level {desired_level} 0 1 1 {node_ID} 1
 $ mattertool levelcontrol read current-level 1 1 // Returns 10
 ```
 
-For more information on running a Silicon Labs lighting example on a Thunderboard Sense 2 see you can view documentation in the Silicon Labs Matter GitHub Repo.
+For more information on running a Silicon Labs lighting example on a Thunderboard Sense 2 you can view documentation in the Silicon Labs Matter GitHub Repo.
 
 ## Defining a Custom Cluster
 

sld250-matter-references/find-raspi.md

@@ -17,7 +17,7 @@ Use nmap with the following command:
     $ sudo nmap -sn <subnet>.0/24`
 ```
 
-Example: `sudo nmap -sn 1-.4.148.0/24`, Among other returned values, you will see something: 
+Example: `sudo nmap -sn 10.4.148.0/24`, Among other returned values, you will see something: 
 
 ```shell
    $ Nmap scan report for ubuntu.silabs.com (10.4.148.44)
@@ -37,7 +37,7 @@ Alternatively, use Arp with the following command:
 
 ### Windows
 
-In the command prompt, use `nslookup` to fnd your Raspberry Pi.
+In the command prompt, use `nslookup` to find your Raspberry Pi.
 
 Example: `nslookup ubuntu`