From bd7c2de7604038eb679e15ddd417543dc940f3d4 Mon Sep 17 00:00:00 2001 From: Anindita Das Date: Thu, 29 Feb 2024 17:29:04 -0500 Subject: [PATCH 1/2] Updated the text for get-started-api Signed-off-by: Anindita Das Signed-off-by: Anindita Das --- daprdocs/content/en/getting-started/get-started-api.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/daprdocs/content/en/getting-started/get-started-api.md b/daprdocs/content/en/getting-started/get-started-api.md index 8fa005dca6c..0d45fcbe5e1 100644 --- a/daprdocs/content/en/getting-started/get-started-api.md +++ b/daprdocs/content/en/getting-started/get-started-api.md @@ -3,10 +3,11 @@ type: docs title: "Use the Dapr API" linkTitle: "Use the Dapr API" weight: 30 -description: "Run a Dapr sidecar and try out the state API" +description: "Run a Dapr sidecar and try out the state management API" --- -In this guide, you'll simulate an application by running the sidecar and calling the API directly. After running Dapr using the Dapr CLI, you'll: +In this guide, you'll simulate an application by running the sidecar and calling the state management API directly. +After running Dapr using the Dapr CLI, you'll: - Save a state object. - Read/get the state object. @@ -21,7 +22,8 @@ In this guide, you'll simulate an application by running the sidecar and calling ### Step 1: Run the Dapr sidecar -The [`dapr run`]({{< ref dapr-run.md >}}) command launches an application, together with a sidecar. +The [`dapr run`]({{< ref dapr-run.md >}}) command normally runs your application and a Dapr sidecar. In this case, +it will only run the sidecar since you will interact with the state management API directly. Launch a Dapr sidecar that will listen on port 3500 for a blank application named `myapp`: From 74c680d66a1971b21b41ff13460d011ec052b209 Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Fri, 1 Mar 2024 17:05:20 -0800 Subject: [PATCH 2/2] Update daprdocs/content/en/getting-started/get-started-api.md Signed-off-by: Mark Fussell --- daprdocs/content/en/getting-started/get-started-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/getting-started/get-started-api.md b/daprdocs/content/en/getting-started/get-started-api.md index 0d45fcbe5e1..a785812c4d2 100644 --- a/daprdocs/content/en/getting-started/get-started-api.md +++ b/daprdocs/content/en/getting-started/get-started-api.md @@ -23,7 +23,7 @@ After running Dapr using the Dapr CLI, you'll: ### Step 1: Run the Dapr sidecar The [`dapr run`]({{< ref dapr-run.md >}}) command normally runs your application and a Dapr sidecar. In this case, -it will only run the sidecar since you will interact with the state management API directly. +it only runs the sidecar since you are interacting with the state management API directly. Launch a Dapr sidecar that will listen on port 3500 for a blank application named `myapp`: