From 27a4f3c4ca964aa0515a2e31f0616ecd4c2f1ffe Mon Sep 17 00:00:00 2001 From: Engincan VESKE Date: Tue, 1 Apr 2025 19:27:25 +0000 Subject: [PATCH] Update docs/en/framework/infrastructure/timing.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/en/framework/infrastructure/timing.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/en/framework/infrastructure/timing.md b/docs/en/framework/infrastructure/timing.md index abcf0aa8f8..be5569f863 100644 --- a/docs/en/framework/infrastructure/timing.md +++ b/docs/en/framework/infrastructure/timing.md @@ -60,8 +60,7 @@ Configure(options => Write this inside of the `ConfigureServices` method of your [module](../architecture/modularity/basics.md). -> The default `Kind` is `Unspecified`, which actually makes the **Clock** as it doesn't exist at all. Either make it `Utc` or `Local` if you want to get the benefit of the Clock system. - +> The default `Kind` is `Unspecified`, which effectively disables the **Clock** functionality. Either make it `Utc` or `Local` if you want to get the benefit of the Clock system. ### DateTime Normalization Another important function of the `IClock` is to normalize `DateTime` objects.