Merge pull request #147 from TREEcg/Minus-markdown

Few markdown fixes

Author: pietercolpaert

01-tree-specification.bs

@@ -225,7 +225,7 @@ See the [`tree:Relation`](#Relation) definitions in the vocabulary for the speci
 
  - **String comparisons** MUST be performed using Unicode canonical equivalence. Ordering MUST follow case-sensitive Unicode code point order.
  - **IRI comparisons** MUST be treated as simple literal comparisons, consistent with the rules defined for the [ORDER BY operation in the SPARQL specification](https://www.w3.org/TR/sparql11-query/#modOrderBy).
- - **`xsd:dateTime` literals without a timezone comparisons** MUST be performed by interpreting the `xsd:dateTime` literal as a period of time, with a min inclusive bound of `-14:00` and max exclusive bound of `+14:00`.
+ - <strong><code>xsd:dateTime</code> literals without a timezone comparisons </strong> MUST be performed by interpreting the `xsd:dateTime` literal as a period of time, with a min inclusive bound of `-14:00` and max exclusive bound of `+14:00`.
 
 Note: It is highly recommended that server developers and data producers provide a timezone in their `xsd:dateTime` literals for time comparison.
 

05-profile-specification.bs

@@ -51,14 +51,14 @@ ex:Collection1 a tree:Collection;
 
 ex:Subject1 a ex:Subject ;
             rdfs:label "Subject 1" ;
-			ex:value 2 ;
+            ex:value 2 ;
             ex:linkedTo [ a ex:Subject ] .
 
 # Start of the second member
 ex:Collection1 tree:member ex:Subject2 .
 ex:Subject2 a ex:Subject ;
             rdfs:label "Subject 2" ;
-			ex:value 9 ;
+            ex:value 9 ;
             ex:linkedTo ex:Subject1 .
 # EOF flags the end of the second member
 ```
@@ -67,7 +67,7 @@ ex:Subject2 a ex:Subject ;
 
 The client in this case MUST use a parser that retains triple order as in the original document.
 
-When the profile is set (see [](#profile)), the client MAY implement the profile algorithm and not perform the steps indicated by the Member Extraction Algorithm. In this case, a client MUST assume the document starts with a hypermedia block. 
+When the profile is set (see [profile](#profile)), the client MAY implement the profile algorithm and not perform the steps indicated by the Member Extraction Algorithm. In this case, a client MUST assume the document starts with a hypermedia block. 
 It then follows three simple rules:
  1. From the moment the `tree:member` property is used, a new bundle of member quads will start.
  2. From the moment the base IRI (`<>`) is used in the subject position, or when a `tree:view` property is used, a new block of hypermedia starts.