fix links (#137)

README.md

@@ -20,4 +20,5 @@ Welcome to the Dapr documentation repository. You can learn more about Dapr from
     - **[Getting Started with .NET Actors](https://github.com/dapr/dotnet-sdk/blob/master/docs/get-started-dapr-actor.md)** - Tutorial for developing actor applications using the Dapr .NET SDK including  **[actor samples](https://github.com/dapr/dotnet-sdk/tree/master/samples/Actor)**
      - **[Getting Started with ASP.NET Core](https://github.com/dapr/dotnet-sdk/tree/master/samples/AspNetCore)** - Samples for developing ASP.NET applications using the Dapr .NET SDK
  
-> Note: Dapr is language agnostic and provides a [RESTful HTTP API](./reference/api) in addition to the protobuf clients.
+> Note: Dapr is language agnostic and provides a [RESTful HTTP API](./reference/api/Readme.md) in addition to the protobuf clients.
+

best-practices/troubleshooting/common_issues.md

@@ -99,7 +99,7 @@ To diagnose, view the logs of the sidecar:
 ### I'm getting 404 Not Found responses when calling Dapr
 
 This means you're trying to call an Dapr API endpoint that either doesn't exist or the URL is malformed.
-Look at the Dapr API spec [here](https://github.com/dapr/spec) and make sure you're calling the right endpoint.
+Look at the Dapr API reference [here](../../reference/api/README.md) and make sure you're calling the right endpoint.
 
 ### I don't see any incoming events or calls from other services
 

concepts/README.md

@@ -1,6 +1,6 @@
 # Dapr concepts
 
-This directory contains various Dapr concepts. The goal of these documents is to expand your knowledge on the [Dapr spec](https://github.com/dapr/spec). 
+This directory contains various Dapr concepts. The goal of these documents is to expand your knowledge on the [Dapr spec](../reference/api/README.md).
 
 ## Core Concepts
 

concepts/actor/actor_overview.md

@@ -50,7 +50,7 @@ POST/GET/PUT/DELETE http://localhost:3500/v1.0/actors/<actorType>/<actorId>/meth
 
 You can provide any data for actor method in the request body and response for the request would be in response body which is data from actor call.
 
-Refer [dapr spec](/dapr/spec/blob/master/actors.md) for more details.
+Refer [dapr spec](../../reference/api/actors.md) for more details.
 
 ### Concurrency
 

concepts/actor/actors_features.md

@@ -45,7 +45,7 @@ You can remove state permanently from the saved Actor state by calling
 DELETE http://localhost:3500/v1.0/actors/<actorType>/<actorId>/state/<key>
 ```
 
-Refer [dapr spec](/dapr/spec/blob/master/actors.md) for more details.
+Refer [dapr spec](../../reference/api/actors.md) for more details.
 
 ## Actor Timers and Reminders
 Actors can schedule periodic work on themselves by registering either timers or reminders.
@@ -77,7 +77,7 @@ You can remove the actor timer  by calling
 DELETE http://localhost:3500/v1.0/actors/<actorType>/<actorId>/timers/<name>
 ```
 
-Refer [dapr spec](/dapr/spec/blob/master/actors.md) for more details.
+Refer [dapr spec](../../reference/api/actors.md) for more details.
 
 ### Actor reminders
 
@@ -107,7 +107,7 @@ You can remove the actor reminder by calling
 DELETE http://localhost:3500/v1.0/actors/<actorType>/<actorId>/reminders/<name>
 ```
 
-Refer [dapr spec](/dapr/spec/blob/master/actors.md) for more details.
+Refer [dapr spec](../../reference/api/actors.md) for more details.
 
 
 

concepts/publish-subscribe-messaging/Readme.md

@@ -9,7 +9,7 @@ These implementations are pluggable, and developed outside of the Dapr runtime i
 
 ## Publish/Subcribe API
 
-The API for Publish/Subcribe can be found in the [spec repo](https://github.com/dapr/spec/blob/master/pubsub.md).
+The API for Publish/Subcribe can be found in the [spec repo](../../reference/api/pubsub.md).
 
 ## Behavior and guarantees
 

concepts/service-invocation/service-invocation.md

@@ -25,5 +25,5 @@ Steps 4-5 are the same as the list above.
 
 
 For more information, see:
-- The [Service Invocation Spec](https://github.com/dapr/spec/blob/master/service_invocation.md)
+- The [Service Invocation Spec](../../reference/api/service_invocation.md)
 - A [HowTo]() on Service Invocation

concepts/state-management/state-management.md

@@ -14,7 +14,7 @@ Dapr data stores are pluggable. Dapr ships with [Redis](https://redis.io
 ), [GCP Cloud Spanner](https://cloud.google.com/spanner
 ) and [Cassandra](http://cassandra.apache.org/).
 
-See the Dapr API specification for details on [state manangement API](https://github.com/dapr/spec/blob/master/state.md)
+See the Dapr API specification for details on [state manangement API](../../reference/api/state.md))
 
 > **NOTE:** Dapr prefixes state keys with the ID of the current Dapr instance/sidecar. This allows multiple Dapr instances to share the same state store.
 
@@ -81,8 +81,8 @@ SELECT AVG(value) FROM StateTable WHERE Id LIKE '<dapr-id>-<therometer>-*-temper
 > **NOTE:** Direct queries of the state store are not governed by Dapr concurrency control, since you are not calling through the Dapr runtime. What you see are snapshots of committed data which are acceptable for read-only queries across multiple actors, however writes should be done via the actor instances.
 
 ## References
-* [Spec: Dapr state managment specification](https://github.com/dapr/spec/blob/master/state.md)
-* [Spec: Dapr actors specification](https://github.com/dapr/spec/blob/master/actors.md)
+* [Spec: Dapr state managment specification](../../reference/api/state.md)
+* [Spec: Dapr actors specification](../../reference/api/actors.md)
 * [How-to: Set up Azure Cosmos DB store](../../howto/setup-state-store/setup-azure-cosmosdb.md)
 * [How-to: Query Azure Cosmos DB store](../../howto/query-state-store/query-cosmosdb-store.md) 
 * [How-to: Set up Redis store](../../howto/setup-state-store/setup-redis.md)

howto/query-state-store/query-cosmosdb-store.md

@@ -1,6 +1,6 @@
 # Query Azure Cosmos DB state store
 
-Dapr doesn't transform state values while saving and retriving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec](https://github.com/dapr/spec/blob/master/state.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 retriving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec](../../reference/api/state.md). You can directly interact with the underlying store to manipulate the state data, such querying states, creating aggregated views and making backups.
 
 > **NOTE:** Azure Cosmos DB is a multi-modal database that supports multiple APIs. The default Dapr Cosmos DB state store implementation uses the [Azure Cosmos DB SQL API](https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-getting-started).
 

howto/query-state-store/query-redis-store.md

@@ -1,6 +1,6 @@
 # Query Redis state store
 
-Dapr doesn't transform state values while saving and retriving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec](https://github.com/dapr/spec/blob/master/state.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 retriving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec](../../reference/api/state.md). You can directly interact with the underlying store to manipulate the state data, such 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. 
 

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//specs).
+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.