docs: fix typos (#2996)

* docs: fix typos

Signed-off-by: Loong <[email protected]>

* Update daprdocs/content/en/operations/components/certification-lifecycle.md

Co-authored-by: Hannah Hunter <[email protected]>
Signed-off-by: Loong Dai <[email protected]>

Signed-off-by: Loong <[email protected]>
Signed-off-by: Loong Dai <[email protected]>
Co-authored-by: Hannah Hunter <[email protected]>

Author: daixiang0

daprdocs/content/en/concepts/components-concept.md

@@ -6,7 +6,7 @@ weight: 300
 description: "Modular functionality used by building blocks and applications"
 ---
 
-Dapr uses a modular design where functionality is delivered as a component. Each component has an interface definition. All of the components are interchangable so that you can swap out one component with the same interface for another.
+Dapr uses a modular design where functionality is delivered as a component. Each component has an interface definition. All of the components are interchangeable so that you can swap out one component with the same interface for another.
 
 You can contribute implementations and extend Dapr's component interfaces capabilities via:
 

daprdocs/content/en/operations/components/certification-lifecycle.md

@@ -12,7 +12,7 @@ Certification lifecycle only applies to built-in components and does not apply t
 
 ## Overview
 
-Dapr uses a modular design where functionality is delivered as a component. Each component has an interface definition. All of the components are interchangable so that in ideal scenarios, you can swap out one component with the same interface for another. Each component that is used in production, needs to maintain a certain set of technical requirements that ensure the functional compatibility and robustness of the component.
+Dapr uses a modular design where functionality is delivered as a component. Each component has an interface definition. All of the components are interchangeable, so that in ideal scenarios, you can swap out one component with the same interface for another. Each component used in production maintains a certain set of technical requirements to ensure functional compatibility and robustness.
 
 In general a component needs to be: