update titles, add links, update service invo overview

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

daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md

@@ -92,7 +92,11 @@ The diagram below shows an example of how this works. If you have 1 instance of
 
 ### Pluggable service discovery
 
-Dapr can run on a variety of [hosting platforms]({{< ref hosting >}}). To enable service discovery and service invocation, Dapr uses pluggable [name resolution components]({{< ref supported-name-resolution >}}). For example, the Kubernetes name resolution component uses the Kubernetes DNS service to resolve the location of other applications running in the cluster. Self-hosted machines can use the mDNS name resolution component. The Consul name resolution component can be used in any hosting environment, including Kubernetes or self-hosted.
+Dapr can run on a variety of [hosting platforms]({{< ref hosting >}}). To enable service discovery and service invocation, Dapr uses pluggable [name resolution components]({{< ref supported-name-resolution >}}). For example, the Kubernetes name resolution component uses the Kubernetes DNS service to resolve the location of other applications running in the cluster. 
+
+Self-hosted machines can use the mDNS name resolution component. As an alternative, you can use the SQLite name resolution component to run Dapr on single-node environments and for local development scenarios. Dapr sidecars that are part of the cluster store their information in a SQLite database on the local machine.
+
+The Consul name resolution component can be used in any hosting environment, including Kubernetes or self-hosted.
 
 ### Streaming for HTTP service invocation
 

daprdocs/content/en/operations/configuration/configuration-overview.md

@@ -209,7 +209,7 @@ spec:
       connectionString: "/home/user/.dapr/nr.db"
 ```
 
-See [the Name Resolution spec documentation]({{< ref supported-name-resolution >}}) to learn more about how to configure name resolution per component.
+See [the Name Resolution spec documentation]({{< ref supported-name-resolution >}}) and the [Configuration YAML documentation]({{< ref configuration-schema.md >}}) to learn more about how to configure name resolution per component.
 
 #### Scope secret store access
 

daprdocs/content/en/reference/components-reference/supported-name-resolution/_index.md

@@ -7,6 +7,8 @@ description: The supported name resolution providers to enable Dapr service invo
 no_list: true
 ---
 
+Name resolution is configured via the [Dapr Configuration]({{< ref configuration-overview.md >}}). 
+
 The following components provide name resolution for the service invocation building block.
 
 {{< partial "components/description.html" >}}

daprdocs/content/en/reference/components-reference/supported-name-resolution/nr-kubernetes.md

@@ -1,6 +1,6 @@
 ---
 type: docs
-title: "Kubernetes DNS name resolution provider spec"
+title: "Kubernetes DNS"
 linkTitle: "Kubernetes DNS"
 description: Detailed information on the Kubernetes DNS name resolution component
 ---

daprdocs/content/en/reference/components-reference/supported-name-resolution/nr-mdns.md

@@ -1,6 +1,6 @@
 ---
 type: docs
-title: "mDNS name resolution provider spec"
+title: "mDNS"
 linkTitle: "mDNS"
 description: Detailed information on the mDNS name resolution component
 ---

daprdocs/content/en/reference/components-reference/supported-name-resolution/nr-sqlite.md

@@ -1,6 +1,6 @@
 ---
 type: docs
-title: "SQLite name resolution provider"
+title: "SQLite"
 linkTitle: "SQLite"
 description: Detailed information on the SQLite name resolution component
 ---

daprdocs/content/en/reference/components-reference/supported-name-resolution/setup-nr-consul.md

@@ -1,6 +1,6 @@
 ---
 type: docs
-title: "HashiCorp Consul name resolution provider spec"
+title: "HashiCorp Consul"
 linkTitle: "HashiCorp Consul"
 description: Detailed information on the HashiCorp Consul name resolution component
 ---