diff --git a/concepts/README.md b/concepts/README.md
index 5e4ed136c..98e2159b1 100644
--- a/concepts/README.md
+++ b/concepts/README.md
@@ -4,7 +4,7 @@ This directory contains various Dapr concepts. The goal of these documents is to
 
 ## Core Concepts
 
-* [**Bindings**](./bindings/Readme.md)
+* [**Bindings**](./bindings/README.md)
 
   A binding provides a bi-directional connection to an external cloud/on-premise service or system. Dapr allows you to invoke the external service through the standard Dapr binding API, and it allows your application to be triggered by events sent by the connected service.
 
diff --git a/concepts/bindings/Readme.md b/concepts/bindings/README.md
similarity index 96%
rename from concepts/bindings/Readme.md
rename to concepts/bindings/README.md
index 90cf19266..81ef7774e 100644
--- a/concepts/bindings/Readme.md
+++ b/concepts/bindings/README.md
@@ -3,8 +3,8 @@
 Using bindings, you can trigger your app with events coming in from external systems, or invoke external systems.
 Bindings allow for on-demand, event-driven compute scenarios, and dapr bindings help developers with the following:
 
-* Remove the complexities of connecting to, and polling from, messaging systems such as queues, message buses etc
-* Focus on business logic and not the implementation details of how interact with a system.
+* Remove the complexities of connecting to, and polling from, messaging systems such as queues, message buses, etc.
+* Focus on business logic and not the implementation details of how interact with a system
 * Keep the code free from SDKs or libraries
 * Handles retries and failure recovery
 * Switch between bindings at runtime time
@@ -43,7 +43,7 @@ An optional payload and metadata might be sent with the request.
 In order to receive events from an input binding:
 
 1. Define the component YAML that describes the type of binding and its metadata (connection info, etc.)
-2. Listen on an HTTP endpoint for the incoming event, or use the gRPC proto library to get incoming events.
+2. Listen on an HTTP endpoint for the incoming event, or use the gRPC proto library to get incoming events
 
 Read the [How To](../../howto) section to get started with input bindings.
 
diff --git a/howto/send-events-with-output-bindings/Readme.md b/howto/send-events-with-output-bindings/Readme.md
index 05ba3006a..5b9bfc6c2 100644
--- a/howto/send-events-with-output-bindings/Readme.md
+++ b/howto/send-events-with-output-bindings/Readme.md
@@ -7,7 +7,7 @@ For a compelete sample showing output bindings, visit this [link](<PLACEHOLDER>)
 
 An output binding represents a resource that Dapr will use invoke and send messages to.
 
-For the purpose of this guide, we'll use a Kafka binding. You can find a list of the different binding specs [here](../../concepts/bindings/Readme.md).
+For the purpose of this guide, we'll use a Kafka binding. You can find a list of the different binding specs [here](../../concepts/bindings/README.md).
 
 Create the following YAML file, named binding.yaml, and save this to the /components sub-folder in your application directory.
 
diff --git a/howto/trigger-app-with-input-binding/Readme.md b/howto/trigger-app-with-input-binding/Readme.md
index fe52c102b..279467105 100644
--- a/howto/trigger-app-with-input-binding/Readme.md
+++ b/howto/trigger-app-with-input-binding/Readme.md
@@ -10,7 +10,7 @@ Dapr bindings allow you to:
 * Replace bindings without changing your code
 * Focus on business logic and not the event resource implementation
 
-For more info on bindings, read [this](../../concepts/bindings/Readme.md) link.<br>
+For more info on bindings, read [this](../../concepts/bindings/README.md) link.<br>
 For a complete sample showing bindings, visit this [link](https://github.com/dapr/samples/tree/master/5.bindings).
 
 ## 1. Create a binding