Apply suggestions from code review

Co-authored-by: Mark Fussell <markfussell@gmail.com> Signed-off-by: mikeee <hey@mike.ee>
dapr · Feb 9, 2024 · fa98d6b · fa98d6b
1 parent e9e6774
commit fa98d6b
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/daprdocs/content/en/getting-started/install-dapr-selfhost.md b/daprdocs/content/en/getting-started/install-dapr-selfhost.md
@@ -10,7 +10,7 @@ aliases:
 
 Now that you've [installed the Dapr CLI]({{<ref install-dapr-cli.md>}}), use the CLI to initialize Dapr on your local machine.
 
-To initialize dapr in your local (or remote) kubernetes cluster. [How to initialize dapr with redis and zipkin]({{<ref "kubernetes-deploy.md#install-dapr-from-the-official-dapr-helm-chart-with-development-flag">}})
+To initialize Dapr in your local (or remote) kubernetes cluster for development including the Redis and Zipkin containers listed above see [how to initialize Dapr for development on Kubernetes]({{<ref "kubernetes-deploy.md#install-dapr-from-the-official-dapr-helm-chart-with-development-flag">}})
 
 Dapr runs as a sidecar alongside your application. In self-hosted mode, this means it is a process on your local machine. By initializing Dapr, you:
 

diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md
@@ -77,13 +77,13 @@ The `-k` flag initializes Dapr on the Kubernetes cluster in your current context
 
 Adding the `--dev` flag initializes Dapr on the Kubernetes cluster on your current context with the addition of Redis and Zipkin deployments.
 
-The steps are similar to the above, save for the inclusion of the `--dev` flag being appended to the init command like so:
+The steps are similar to the above, save for the inclusion of the `--dev` flag being appended to the init command:
 
  ```bash
  dapr init -k --dev
  ```
 
-The expected output will be:
+Expected output:
 
 ```bash
 ⌛  Making the jump to hyperspace...
@@ -100,13 +100,13 @@ The expected output will be:
 ✅  Success! Dapr has been installed to namespace dapr-system. To verify, run `dapr status -k' in your terminal. To get started, go here: https://aka.ms/dapr-getting-started
  ```
 
-After a short period of time (or using the `--wait` flag and specifying an amount of time to wait) you should be able to check that the Redis and Zipkin components have been stood up correctly.
+After a short period of time (or using the `--wait` flag and specifying an amount of time to wait) you can check that the Redis and Zipkin components have been deployed to the cluster.
 
 ```bash
 kubectl get pods --namespace default
 ```
 
-Expected Output:
+Expected output:
 
 ```bash
 NAME                              READY   STATUS    RESTARTS   AGE