updates to release notes

Signed-off-by: Hannah Hunter <[email protected]>

daprblog/content/posts/2024/v1.14-release.md

@@ -52,7 +52,7 @@ spec:
 ### Streaming subscriptions (preview)
 [Streaming subscription are a new type of subscription written in code](https://v1-14.docs.dapr.io/developing-applications/building-blocks/pubsub/subscription-methods/). Streaming subscriptions are dynamic, meaning they allow for adding or removing subscriptions at runtime. They do not require a subscription HTTP endpoint in your application (that is required by the current programmatic and declarative subscriptions), making them easy to configure in code. Streaming subscriptions also do not require an app to be configured with the sidecar to receive messages. These are an [incredibly easy way to configure topic subscriptions](https://v1-14.docs.dapr.io/developing-applications/building-blocks/pubsub/subscription-methods/#streaming-subscriptions) for your app.
 
-### Actor multi-tenancy with namespacing
+### Actor multi-tenancy with namespacing 
 Namespacing in Dapr provides [isolation](https://v1-14.docs.dapr.io/concepts/isolation-concept/), and thus multi-tenancy. With [actor namespacing](https://v1-14.docs.dapr.io/developing-applications/building-blocks/actors/namespaced-actors/), the same actor type can be deployed into different namespaces. You can then call instances of these actors within the same namespace. Each namespaced actor deployment must use its own separate state store, especially if the same actor type is used across namespaces.
 
 
@@ -73,11 +73,11 @@ When using the [outbox pattern](https://v1-14.docs.dapr.io/developing-applicatio
 The ability to invoke non-Dapr endpoints using the Dapr [Service invocation API](https://docs.dapr.io/developing-applications/building-blocks/service-invocation/howto-invoke-non-dapr-endpoints/)is now stable.
 
 ### Dapr Shared ([new preview repo in Dapr org](https://github.com/dapr/dapr-shared/blob/main/README.md))
-Although not part of the Dapr runtime v1.14 release, [Dapr Shared provides alternative deployment choices for Dapr](https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-dapr-shared/).
+Although not part of the Dapr runtime v1.14 release, [Dapr Shared provides alternative deployment choices for Dapr](https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-dapr-shared/). 
 
-Dapr, by default, is injected as a sidecar to enable the Dapr APIs for your applications for the best availability and reliability. Dapr Shared enables two alternative deployment strategies to create Dapr applications using a **Kubernetes Daemonset for a per-node deployment** or a **Deployment for a per-cluster** deployment.
+Dapr, by default, is injected as a sidecar to enable the Dapr APIs for your applications for the best availability and reliability. Dapr Shared enables two alternative deployment strategies to create Dapr applications using a **Kubernetes Daemonset for a per-node deployment** or a **Deployment for a per-cluster** deployment. 
 
-For example, Dapr Shared can be used to reduce resource usage in a cluster or to make a simpler testing deployment environment.
+For example, Dapr Shared can be used to reduce resource usage in a cluster or to make a simpler testing deployment environment. 
 
 ### Support for cryptography api in the python sdk
 The python-sdk now has support for the cryptography api.
@@ -329,6 +329,7 @@ To upgrade Dapr using Helm, run:
 ```
 helm repo add dapr https://dapr.github.io/helm-charts/
 helm repo update
+
 helm upgrade dapr dapr/dapr --version 1.14 --namespace=dapr-system --wait
 ```
 
@@ -346,7 +347,9 @@ You can use Helm 3 to install Dapr:
 ```
 helm repo add dapr https://dapr.github.io/helm-charts/
 helm repo update
+
 kubectl create namespace dapr-system
+
 helm install dapr dapr/dapr --version 1.14 --namespace dapr-system --wait
 ```
 
@@ -388,4 +391,4 @@ Actors are now namespaced, meaning that cross-namespace actor invocation is no l
 
 ## Deprecation Notices
 
-None.
+None.