Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Mark Fussell <[email protected]>
Signed-off-by: Josh van Leeuwen <[email protected]>
  • Loading branch information
JoshVanL and msfussell authored Jan 9, 2024
1 parent ad8835c commit 1a24364
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions daprdocs/content/en/concepts/components-concept.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,11 +54,11 @@ For more information read [Pluggable components overview]({{< ref "pluggable-com

## Hot Reloading

With the [`HotReload` feature enabled]({{< ref "support-preview-features.md" >}}), Components are able to be "hot reloaded" at runtime.
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.
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.
There will be a short period of time where the component is unavailable during the duration of the reload until the component is reinitialized.
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

Expand Down

0 comments on commit 1a24364

Please sign in to comment.