From 8eee5b5d7b7eb487889cb1d83c4fed388bd7bd80 Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Wed, 29 May 2024 13:40:45 -0400 Subject: [PATCH] fix links Signed-off-by: Hannah Hunter --- .../building-blocks/scheduler/scheduler-overview.md | 4 ++-- .../content/en/operations/support/support-preview-features.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/scheduler/scheduler-overview.md b/daprdocs/content/en/developing-applications/building-blocks/scheduler/scheduler-overview.md index b568c1019c5..983af48cfe8 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/scheduler/scheduler-overview.md +++ b/daprdocs/content/en/developing-applications/building-blocks/scheduler/scheduler-overview.md @@ -16,7 +16,7 @@ The Scheduler API works as an orchestrator for scheduling jobs in the future, e The Scheduler consists of two parts that work together to seamlessly schedule jobs across all of Dapr's API building blocks: - The Scheduler building block -- [The Scheduler control plane service]({{< ref scheduler.md >}}) +- [The Scheduler control plane service]({{< ref "concepts/dapr-services/scheduler.md" >}}) This article covers the Scheduler API building block. @@ -55,5 +55,5 @@ You can try out the Scheduler building block directly in your application. After ## Next steps - [Learn how to use the scheduler in your environment]({{< ref howto-use-scheduler.md >}}) -- [Learn more about the Scheduler control plane service]({{< ref scheduler.md >}}) +- [Learn more about the Scheduler control plane service]({{< ref "concepts/dapr-services/scheduler.md" >}}) - [Scheduler API reference]({{< ref scheduler_api.md >}}) diff --git a/daprdocs/content/en/operations/support/support-preview-features.md b/daprdocs/content/en/operations/support/support-preview-features.md index 933ff96b7c6..ae7dbdff71d 100644 --- a/daprdocs/content/en/operations/support/support-preview-features.md +++ b/daprdocs/content/en/operations/support/support-preview-features.md @@ -23,4 +23,4 @@ For CLI there is no explicit opt-in, just the version that this was first made a | **Actor State TTL** | Allow actors to save records to state stores with Time To Live (TTL) set to automatically clean up old data. In its current implementation, actor state with TTL may not be reflected correctly by clients, read [Actor State Transactions]({{< ref actors_api.md >}}) for more information. | `ActorStateTTL` | [Actor State Transactions]({{< ref actors_api.md >}}) | v1.11 | | **Transactional Outbox** | Allows state operations for inserts and updates to be published to a configured pub/sub topic using a single transaction across the state store and the pub/sub | N/A | [Transactional Outbox Feature]({{< ref howto-outbox.md >}}) | v1.12 | | **Component Hot Reloading** | Allows for Dapr-loaded components to be "hot reloaded". A component spec is reloaded when it is created/updated/deleted in Kubernetes or on file when running in self-hosted mode. Ignores changes to actor state stores and workflow backends. | `HotReload`| [Hot Reloading]({{< ref components-concept.md >}}) | v1.13 | -| **Scheduler reminders** | While [Scheduler]({{< ref scheduler.md >}}) is deployed by default, scheduler reminders (used for scheduling actor reminders) are enabled through a preview feature and needs a feature flag. | `SchedulerReminders`| [Scheduler reminders]({{< ref "scheduler-overview.md#scheduler-reminders" >}}) | v1.14 | \ No newline at end of file +| **Scheduler reminders** | While [Scheduler]({{< ref "concepts/dapr-services/scheduler.md" >}}) is deployed by default, scheduler reminders (used for scheduling actor reminders) are enabled through a preview feature and needs a feature flag. | `SchedulerReminders`| [Scheduler reminders]({{< ref "scheduler-overview.md#scheduler-reminders" >}}) | v1.14 | \ No newline at end of file