Merge branch 'v0.11' into v1.0-rc2

README.md

@@ -50,9 +50,10 @@ hugo server --disableFastRender
 3. Navigate to `http://localhost:1313/docs`
 
 ## Update docs
+1. Fork repo into your account
 1. Create new branch
-1. Commit and push changes to content
-1. Submit pull request to `master`
+1. Commit and push changes to forked branch
+1. Submit pull request from downstream branch to the upstream branch for the correct version you are targeting
 1. Staging site will automatically get created and linked to PR to review and test
 
 ## Code of Conduct

daprdocs/content/en/contributing/contributing-docs.md

@@ -105,8 +105,19 @@ This shortcode will link to a specific page:
 ```md
 {{</* ref "page.md" */>}}
 ```
+> Note that all pages and folders need to have globally unique names in order for the ref shortcode to work properly. If there are duplicate names the build will break and an error will be thrown.
 
-> Note that all pages and folders need to have globally unique names in order for the ref shortcode to work properly.
+#### Referencing sections in other pages
+
+To reference a specific section in another page, add `#section-short-name` to the end of your reference.
+
+As a general rule, the section short name is the text of the section title, all lowercase, with spaces changed to "-". You can check the section short name by visiting the website page, clicking the link icon (🔗) next to the section, and see how the URL renders in the nav bar. The content after the "#" is your section shortname.
+
+As an example, for this specific section the complete reference to the page and section would be:
+
+```md
+{{</* ref "contributing-docs.md#referencing-sections-in-other-pages" */>}}
+```
 
 ### Images
 The markdown spec used by Docsy and Hugo does not give an option to resize images using markdown notation. Instead, raw HMTL is used.

daprdocs/content/en/developing-applications/building-blocks/actors/actors-background.md

@@ -54,7 +54,7 @@ To provide scalability and reliability, actors instances are distributed through
 Actors are distributed across the instances of the actor service, and those instance are distributed across the nodes in a cluster. Each service instance contains a set of actors for a given actor type.
 
 ### Actor placement service
-The Dapr actor runtime manages distribution scheme and key range settings for you. This is done by the actor `Placement` service. When a new instance of a service is created, the corresponding Dapr runtime register the actor types it can create and the `Placement` service calculates the partitioning across all the instances for a given actor type. This table of partition information for each actor type is updated and stored in each Dapr instance running in the environment and can change dynamically as new instance of actor services are created and destroyed. This is shown in the diagram below.
+The Dapr actor runtime manages distribution scheme and key range settings for you. This is done by the actor `Placement` service. When a new instance of a service is created, the corresponding Dapr runtime registers the actor types it can create and the `Placement` service calculates the partitioning across all the instances for a given actor type. This table of partition information for each actor type is updated and stored in each Dapr instance running in the environment and can change dynamically as new instance of actor services are created and destroyed. This is shown in the diagram below.
 
 <img src="/images/actors_background_placement_service_registration.png" width=600>
 
@@ -67,11 +67,11 @@ When a client calls an actor with a particular id (for example, actor id 123), t
 * By default, actors are randomly placed into pods resulting in uniform distribution.
 * Because actors are randomly placed, it should be expected that actor operations always require network communication, including serialization and deserialization of method call data, incurring latency and overhead.
 
-Note: The Dapr actor Placement service is only used for actor placement and therefore is not needed if your services are not using Dapr actors. The Placement service can run in all hosting environments for example, self hosted, Kubernetes
+Note: The Dapr actor Placement service is only used for actor placement and therefore is not needed if your services are not using Dapr actors. The Placement service can run in all [hosting environments]({{< ref hosting >}}), including self-hosted and Kubernetes.
 
 ## Actor communication
 
-You can interact with Dapr to invoke the actor method by calling HTTP/gRPC endpoint
+You can interact with Dapr to invoke the actor method by calling HTTP/gRPC endpoint.
 
 ```bash
 POST/GET/PUT/DELETE http://localhost:3500/v1.0/actors/<actorType>/<actorId>/<method/state/timers/reminders>

daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md

@@ -97,6 +97,7 @@ Event delivery guarantees are controlled by the binding implementation. Dependin
 
 ## References
 
-* Binding [API](https://github.com/dapr/docs/blob/master/reference/api/bindings_api.md)
-* Binding [Components](https://github.com/dapr/docs/tree/master/concepts/bindings)
-* Binding [Detailed specifications](https://github.com/dapr/docs/tree/master/reference/specs/bindings)
+* [Bindings building block]({{< ref bindings >}})
+* [Bindings API]({{< ref bindings_api.md >}})
+* [Components concept]({{< ref components-concept.md >}})
+* [Supported bindings]({{< ref supported-bindings >}})

daprdocs/content/en/developing-applications/building-blocks/pubsub/howto-publish-subscribe.md

@@ -68,8 +68,13 @@ spec:
 ## Step 2: Subscribe to topics
 
 Dapr allows two methods by which you can subscribe to topics:
+
 - **Declaratively**, where subscriptions are are defined in an external file.
-- **Programatically**, where subscriptions are defined in user code
+- **Programmatically**, where subscriptions are defined in user code
+
+{{% alert title="Note" color="primary" %}}
+Both declarative and programmatic approaches support the same features. The declarative approach removes the Dapr dependancy from the user code and allows for the use of an existing application to subscribe to topics. The programmatic approach implements the subscription in user code.
+{{% /alert %}}
 
 ### Declarative subscriptions
 

daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-redis-store.md

@@ -6,7 +6,7 @@ weight: 2000
 description: "Use Redis as a backend state store"
 ---
 
-Dapr doesn't transform state values while saving and retrieving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec]({{<ref state_api.md>}}). You can directly interact with the underlying store to manipulate the state data, such querying states, creating aggregated views and making backups.
+Dapr doesn't transform state values while saving and retrieving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec]({{<ref state_api.md>}}). You can directly interact with the underlying store to manipulate the state data, such as querying states, creating aggregated views and making backups.
 
 >**NOTE:** The following examples uses Redis CLI against a Redis store using the default Dapr state store implementation.
 

daprdocs/content/en/operations/components/setup-secret-store/supported-secret-stores/azure-keyvault-managed-identity.md

@@ -100,16 +100,16 @@ description: How to configure Azure Key Vault and Kubernetes to use Azure Manage
       name: [you managed identity name]
     spec:
       type: 0
-      ResourceID: [you managed identity id]
-      ClientID: [you managed identity Client ID]
+      resourceID: [you managed identity id]
+      clientID: [you managed identity Client ID]
     ---
     apiVersion: "aadpodidentity.k8s.io/v1"
     kind: AzureIdentityBinding
     metadata:
       name: [you managed identity name]-identity-binding
     spec:
-      AzureIdentity: [you managed identity name]
-      Selector: [you managed identity selector]
+      azureIdentity: [you managed identity name]
+      selector: [you managed identity selector]
     ```
 
 10. Deploy the azure-identity-config.yaml:

daprdocs/content/en/operations/components/setup-state-store/supported-state-stores/setup-sqlserver.md

@@ -14,7 +14,7 @@ description: Detailed information on the SQL Server state store component
 In order to setup SQL Server as a state store, you will need the following properties:
 
 - **Connection String**: the SQL Server connection string. For example: server=localhost;user id=sa;password=your-password;port=1433;database=mydatabase;
-- **Schema**: The database schema do use (default=dbo). Will be created if not exists
+- **Schema**: The database schema to use (default=dbo). Will be created if not exists
 - **Table Name**: The database table name. Will be created if not exists
 - **Indexed Properties**: Optional properties from json data which will be indexed and persisted as individual column