small updates per Mark

Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>

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

@@ -103,10 +103,11 @@ Lock components are used as a distributed lock to provide mutually exclusive acc
 
 ### Workflows
 
-A [workflow]({{< ref workflow-overview.md >}}) is custom application logic that defines business process or data flow in a reliable way across mulitple microservices. The workflow API is exposed by a [lightweight, embedded workflow engine]({{< ref "operations/components/workflow-engine/workflow-engine.md" >}}) in the Dapr sidecar, allowing you to easily integrate with existing Dapr building blocks. 
+A [workflow]({{< ref workflow-overview.md >}}) is custom application logic that defines a reliable business process or data flow. Workflow components are workflow runtimes (or engines) that run the business logic written for that workflow and store their state into a state store.  
 
 - [List of supported workflow components]({{< ref supported-workflows >}})
-- Workflow implementations
+- [Workflow implementations]()
+- [Binding implementations](https://github.com/dapr/components-contrib/tree/master/workflows)
 
 ### Middleware
 

daprdocs/content/en/concepts/faq.md

@@ -27,18 +27,6 @@ Creating a new actor follows a local call like `http://localhost:3500/v1.0/actor
 
 The Dapr runtime SDKs have language-specific actor frameworks. For example, the .NET SDK has C# actors. The goal is for all the Dapr language SDKs to have an actor framework. Currently .NET, Java, Go and Python SDK have actor frameworks.
 
-## Workflows
-
-### Differences between Dapr Workflows, authoring APIs, and the management API
-
-TODO
-
-### What is the relationship between Dapr Workflows and the Durable task framework?
-
-TODO
-
-## Developer language SDKs and frameworks
-
 ### Does Dapr have any SDKs I can use if I want to work with a particular programming language or framework?
 
 To make using Dapr more natural for different languages, it includes [language specific SDKs]({{<ref sdks>}}) for Go, Java, JavaScript, .NET,  Python, PHP, Rust and C++. These SDKs expose the functionality in the Dapr building blocks, such as saving state, publishing an event or creating an actor, through a typed language API rather than calling the http/gRPC API. This enables you to write a combination of stateless and stateful functions and actors all in the language of your choice. And because these SDKs share the Dapr runtime, you get cross-language actor and functions support.

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

@@ -6,13 +6,15 @@ weight: 1000
 description: "Overview of the workflow building block"
 ---
 
-With Dapr workflows, you can automate and orchestrate tasks within your application. The workflow feature provides a developer-friendly programming model for authoring workflows as code in a way that abstracts away the complexities of messaging, state management, and failure handling.
+With workflows, you can orchestrate tasks or business logic within your application, making them reliable and restartable. Workflows provide a programming model for authoring code that abstracts away the complexities of messaging, state management, and failure handling.
 
-The workflow feature is comprised of the Workflow API and the workflow components that allow for authoring workflows naitively in Dapr or through external 3rd party workflow applications.
+## Workflow building block
 
-<img src="/images/concepts-building-blocks.png" width=250>
+The workflow building block:
 
-## Workflow API
+- Provides a workflow API for running workflows
+- An built-in workflow runtime to write Dapr workflows (of type workflow.dapr)
+- Integrates with various workflow runtimes as components, for example Temporal workflows.
 
 *To Do:*
 - *Add diagram of how workflow API works?*
@@ -23,7 +25,7 @@ The workflow feature is comprised of the Workflow API and the workflow component
 
 ## Features
 
-*To Do*
+Start, Terminate and X any workflow
 
 
 ## Next steps