diff --git a/daprdocs/content/en/concepts/components-concept.md b/daprdocs/content/en/concepts/components-concept.md
index 48365186d..db5122e0a 100644
--- a/daprdocs/content/en/concepts/components-concept.md
+++ b/daprdocs/content/en/concepts/components-concept.md
@@ -57,7 +57,7 @@ For more information read [Pluggable components overview]({{< ref "pluggable-com
 With the [`HotReload` feature enabled]({{< ref "support-preview-features.md" >}}), components are able to be "hot reloaded" at runtime.
 This means that you can update component configuration without restarting the Dapr runtime.
 Component reloading happens when a component resource is created, updated, or deleted, either in the Kubernetes API or in Self Hosted mode when a file is changed in the `resources` directory.
-When a component is updated, the Component is first closed, and then reinitialized using the new configuration.
+When a component is updated, the component is first closed, and then reinitialized using the new configuration.
 There is a short period of time where the component is unavailable during the duration of the reload until the component is reinitialized.
 
 ## Available component types