Update concepts docs

daprdocs/content/en/concepts/components-concept.md

@@ -14,34 +14,42 @@ Dapr uses a modular design where functionality is delivered as a component. Each
 
  The following are the component types provided by Dapr:
 
-* [State stores](https://github.com/dapr/components-contrib/tree/master/state)
-* [Service discovery name resolution](https://github.com/dapr/components-contrib/tree/master/nameresolution)
-* [Middleware](https://github.com/dapr/components-contrib/tree/master/middleware)
-* [Pub/sub brokers](https://github.com/dapr/components-contrib/tree/master/pubsub)
-* [Bindings](https://github.com/dapr/components-contrib/tree/master/bindings)
-* [Secret stores](https://github.com/dapr/components-contrib/tree/master/secretstores)
-
-
 ## State stores
 
 State store components are databases that store key-value pairs as part of the [state management]({{< ref "state-management-overview.md" >}}) building block.
 
+- [List of state stores]({{< ref supported-state-stores >}})
+- [State store implementations](https://github.com/dapr/components-contrib/tree/master/state)
+
 ## Service discovery
 
 Service discovery components are used with the [service invocation]({{<ref "service-invocation-overview.md">}}) building block to integrate with the hosting environment to provide service-to-service discovery. For example, the Kubernetes service discovery component integrates with the Kubernetes DNS service and self hosted uses mDNS.
 
+- [Service discovery name resolution implementations](https://github.com/dapr/components-contrib/tree/master/nameresolution)
+
 ## Middleware
 
 Dapr allows custom [middleware]({{<ref "middleware-concept.md">}})  to be plugged into the request processing pipeline. Middleware can perform additional actions on a request, such as authentication, encryption and message transformation before the request is routed to the user code, or before the request is returned to the client. The middleware components are used with the [service invocation]({{<ref "service-invocation-overview.md">}}) building block.
 
+- [Middleware implementations](https://github.com/dapr/components-contrib/tree/master/middleware)
+
 ## Pub/sub brokers
 
 Pub/sub broker components are message busses that can pass messages to/from services as part of the [publish & subscribe]({{< ref pubsub-overview.md >}}) building block.
 
+- [List of pub/sub brokers]({{< ref supported-pubsub >}})
+- [Pub/sub broker implementations](https://github.com/dapr/components-contrib/tree/master/pubsub)
+
 ## Bindings
 
 External resources can connect to Dapr in order to trigger a service or be invoked from a service as part of the [bindings]({{< ref bindings-overview.md >}}) building block.
 
+- [List of supported bindings]({{< ref supported-bindings >}})
+- [Binding implementations](https://github.com/dapr/components-contrib/tree/master/bindings)
+
 ## Secret stores
 
 In Dapr, a [secret]({{<ref "secrets-overview.md">}}) is any piece of private information that you want to guard against unwanted users. Secrets stores, used to store secrets, are Dapr components and can be used by any of the building blocks.
+
+- [List of supported secret stores]({{< ref supported-secret-stores >}})
+- [Secret store implementations](https://github.com/dapr/components-contrib/tree/master/secretstores)

daprdocs/content/en/concepts/terminology.md

@@ -15,7 +15,7 @@ This page details all of the common terms you may come across in the Dapr docs.
 | Component | A modular piece of functionality that make up, either by itself or with a collection of other components, a Dapr building block. | [Dapr components]({{< ref components-concept.md >}})
 | Configuration | A YAML file declaring all of the settings for Dapr sidecars and the Dapr control plane. It is here where you can configure mTLS, tracing, and middleware. | [Dapr configuration]({{< ref configuration-concept.md >}})
 | Dapr | Distributed Application Runtime. | [Dapr overview]({{< ref overview.md >}})
+| Dapr control plane | A collection of services that are part of a Dapr installation on a hosting platform such as a Kubernetes cluster. Allow Dapr enabled applications to run on that platform and handles Dapr capabilities such as service discovery or sidecar injection. | [Self-hosted overview]({{< ref self-hosted-overview >}})<br />[Kubernetes overview]({{< ref kubernetes-overview >}})
 | Self-hosted | Your local Windows/macOS/Linux machine where you run your applications with Dapr. Dapr provides capabilities to run on your machine in "self-hosted" mode. | [Self-hosted mode]({{< ref self-hosted-overview.md >}})
-| Service | A running application or binary. Can be used to refer to your application, or a Dapr applicaiton.
+| Service | A running application or binary. Can be used to refer to your application, or a Dapr application.
 | Sidecar | A program that runs along side your application as a separate binary or pod. | [Sidecar pattern](https://docs.microsoft.com/en-us/azure/architecture/patterns/sidecar)
-| System services | Applications that run as part of the Dapr control plane, which take care of the various jobs that Dapr handles such as service discovery or sidecar injection. | [Self-hosted overview]({{< ref self-hosted-overview >}})<br />[Kubernetes overview]({{< ref kubernetes-overview >}})