Fix some documentation typos (#13067)

README.md

@@ -89,13 +89,13 @@ to help achieve our interoperability architectural goal. Matter will initially
 support Wi-Fi and Thread for core, operational communications and Bluetooth Low
 Energy (BLE) to simplify device commissioning and setup.
 
-The Application Layer can be further broken down seven main components:
+The Application Layer can be further broken down into seven main components:
 
 ![Matter Stack Architecture](docs/images/CHIP_Arch_Pyramid.png)
 
 1. **Application:** High order business logic of a device. For example, an
  application that is focused on lighting might contain logic to handle turning
- on/off the bulb as well its color characteristics.
+ on/off the bulb as well as its color characteristics.
 
 2. **Data Model:** Data primitives that help describe the various
  functionalities of the devices. The Application operates on these data
@@ -116,7 +116,7 @@ The Application Layer can be further broken down seven main components:
 
 6. **Message Framing & Routing:** With an interaction encrypted and signed, the
  Message Layer constructs the payload format with required and optional header
- fields; which specify properties of the message as well some routing
+ fields; which specify properties of the message as well as some routing
  information.
 
 7. **IP Framing & Transport Management:** After the final payload has been

docs/PROJECT_FLOW.md

@@ -9,7 +9,7 @@ repository.
 Matter uses issues as simple problem descriptions or feature requests. In
 general, all work contributed to the repository in the form of pull requests
 (PR) should be under the auspices of some open issue. This may seem onerous and
-in some cases duplicative, so consider these guidelines when deciding whether to
+in some cases duplicative, so consider these guidelines when deciding whether
 you can get away with not creating an issue:
 
 - Trivial fixes: issues can function as TODO lists, simple reminders that

docs/QUICK_START.md

@@ -2,8 +2,8 @@
 
 ## Demo Overview
 
-The Matter reference implementation contains support for a number examples and
-platforms.
+The Matter reference implementation contains support for a number of examples
+and platforms.
 
 ## Wi-Fi Nodes
 

docs/STYLE_GUIDE.md

@@ -75,7 +75,7 @@ $ git clone https://github.com/project-chip/connectedhomeip.git
 
 ### Terminal prompts
 
-If you need use a full terminal prompt with username and hostname, use the
+If you need to use a full terminal prompt with username and hostname, use the
 format of `root@{hostname}{special-characters}#`.
 
 For example, when logged into a Docker container, you might have a prompt like

docs/guides/BUILDING.md

@@ -280,7 +280,7 @@ all of the target instances. For example:
 gn desc out/unified '//src/controller(//build/toolchain/host:linux_x64_clang)'
 ```
 
-Note: Some platforms that can be build as part of the unified build require
+Note: Some platforms that can be built as part of the unified build require
 downloading additional SDKs. To add these to the build, the location of the SDK
 installation must be provided as a build argument. For example, to add the
 Simplelink cc13x2_26x2 examples to the unified build, install the

docs/style/DOXYGEN.adoc

@@ -165,7 +165,7 @@ Objective C{plusplus}. Adapt as appropriate for Perl, Python and Shell.
  * interpreted and parsed. If 0 or 16, the string may
  * be hexadecimal and prefixed with "0x". Otherwise, a 0
  * is implied as 10 unless a leading 0 is encountered in
- * which 8 is implied.
+ * which case 8 is implied.
  *
  * @retval 0 on success.
  * @retval #EINVAL if the given base contains an unsupported value or if no

docs/style/coding/CODING_STYLE_GUIDE.adoc

@@ -273,7 +273,7 @@ Heap-based resource allocation should be avoided.
 As emphasized throughout this document, the software produced by Project
 CHIP is consumed both inside and outside Project CHIP, across a variety
 of platforms. The capabilities of these platforms are broad, spanning
-soft real-time, deeply-embedded systems based on based on RTOSes that
+soft real-time, deeply-embedded systems based on RTOSes that
 may cover life safety and/or physical security applications to richer,
 softly-embedded systems based on non-RTOS platforms such as Darwin or
 Linux. While the latter are apt to have fully-functional heaps, the