fix some links (#170)

* fix links to the document

* fix link to terminology.md

* fix link: linked to opentracing/specification repository's specification.md

* fix another link

* fix link to external document

* fix more links

work_in_progress/opencensus/StandardResources.md

@@ -1,7 +1,7 @@
 # Standard Resources
 
 This page lists the standard resource types in OpenCensus. For more details on how resources can 
-be combined see [this](Resource.md).
+be combined see [this](../specification/resource/Resource.md).
 
 OpenCensus defines these fields.
  * [Compute Unit](#compute-unit)
@@ -28,7 +28,7 @@ Resources defining a compute unit (e.g. Container, Process, Lambda Function).
 ### Container
 **type:** `container`
 
-**Description:** A container instance. This resource can be [merged](Resource.md#Merging) with a
+**Description:** A container instance. This resource can be [merged](../specification/resource/Resource.md#Merging) with a
 deployment service resource, a compute instance resource, and an environment resource.
 
 | Label  | Description  | Example  |
@@ -43,7 +43,7 @@ Resources defining a deployment service (e.g. Kubernetes).
 ### Kubernetes
 **type:** `k8s`
 
-**Description:** A Kubernetes resource. This resource can be [merged](Resource.md#Merging) with
+**Description:** A Kubernetes resource. This resource can be [merged](../specification/resource/Resource.md#Merging) with
 a compute instance resource, and/or an environment resource.
 
 | Label  | Description  | Example  |
@@ -59,7 +59,7 @@ Resources defining a computing instance (e.g. host).
 **type:** `host`
 
 **Description:** A host is defined as a general computing instance. This resource should be
-[merged](Resource.md#Merging) with an environment resource.
+[merged](../specification/resource/Resource.md#Merging) with an environment resource.
 
 
 | Label  | Description  | Example  |

work_in_progress/opentracing/semantic_conventions.md

@@ -1,6 +1,6 @@
 # Semantic Conventions
 
-The [OpenTracing Specification](./specification.md) describes the overarching language-neutral data model and API guidelines for OpenTracing. That data model includes the related concepts of **Span Tags** and **(structured) Log Fields**; though these terms are defined in the specification, there is no guidance there about standard Span tags or logging keys.
+The [OpenTracing Specification](https://github.com/opentracing/specification/blob/master/specification.md) describes the overarching language-neutral data model and API guidelines for OpenTracing. That data model includes the related concepts of **Span Tags** and **(structured) Log Fields**; though these terms are defined in the specification, there is no guidance there about standard Span tags or logging keys.
 
 Those semantic conventions are described by this document. The document is divided into two sections: first, tables listing all standard Span tags and logging keys; then guidance about how to combine these to model certain important semantic concepts.
 
@@ -14,7 +14,7 @@ Changes to this file affect the OpenTracing specification version. Additions sho
 
 Span tags apply to **the entire Span**; as such, they apply to the entire timerange of the Span, not a particular moment with a particular timestamp: those sorts of events are best modelled as Span log fields (per the table in the next subsection of this document).
 
-> Work in progress! Please note, that the list below only contains attributes that aren't contained in the [OpenTelemetry main spec](../semantic-conventions.md) (yet):
+> Work in progress! Please note, that the list below only contains attributes that aren't contained in the [OpenTelemetry main spec](../../semantic-conventions.md) (yet):
 
 | Span tag name | Type | Notes and examples |
 |:--------------|:-----|:-------------------|
@@ -50,7 +50,7 @@ The following Span tags combine to model RPCs:
 
 ### Message Bus
 
-A message bus is asynchronous, and therefore the relationship type used to link a Consumer Span and a Producer Span would be **Follows From** (see [References between Spans](./specification.md#references-between-spans) for more information on relationship types).
+A message bus is asynchronous, and therefore the relationship type used to link a Consumer Span and a Producer Span would be **Follows From** (see [References between Spans](https://github.com/opentracing/specification/blob/master/specification.md#references-between-spans) for more information on relationship types).
 
 The following Span tags combine to model message bus based communications:
 

work_in_progress/specification/trace/Span.md

@@ -1,7 +1,7 @@
 # Span
  
 
-... parts of this document moved to [terminology.md](../terminology.md) ...
+... parts of this document moved to [terminology.md](../../../terminology.md) ...
 
 A span contains a SpanContext and allows users to record tracing events based on the data model 
 defined [here][SpanDataModel].

work_in_progress/typedspans/README.md

@@ -42,7 +42,7 @@ See [this document by @discostu105](https://docs.google.com/spreadsheets/d/1H0S0
 Represents an outbound HTTP request.
 
 ##### Attributes
-These attributes are not covered in the [main spec](../semantic-conventions.md):
+These attributes are not covered in the [main spec](../../semantic-conventions.md):
 
 - Route
 - User Agent
@@ -55,7 +55,7 @@ Represents an inbound HTTP request.
 
 ##### Attributes
 
-These attributes are not covered in the [main spec](../semantic-conventions.md):
+These attributes are not covered in the [main spec](../../semantic-conventions.md):
 
 - User Agent
 - Webserver Name
@@ -69,7 +69,7 @@ Represents a database call.
 
 ##### Attributes
 
-These attributes are not covered in the [main spec](../semantic-conventions.md):
+These attributes are not covered in the [main spec](../../semantic-conventions.md):
 
 - Channel Type (e.g. TCP)
 
@@ -78,7 +78,7 @@ Represents an outbound gRPC request.
 
 ##### Attributes
 
-These attributes are not covered in the [main spec](../semantic-conventions.md):
+These attributes are not covered in the [main spec](../../semantic-conventions.md):
 
 - Channel Type (e.g. TCP)
 
@@ -87,7 +87,7 @@ Represents an inbound gRPC request.
 
 ##### Attributes
 
-These attributes are not covered in the [main spec](../semantic-conventions.md):
+These attributes are not covered in the [main spec](../../semantic-conventions.md):
 
 - Channel Type (e.g. TCP)