Merge pull request #33 from toml-lang/rc-1.0.0-user-content

Remove "user-content-" from internal document links

specs/en/v1.0.0.md

@@ -17,25 +17,25 @@ should be easy to parse into data structures in a wide variety of languages.
 Table of contents
 -----------------
 
-- [Spec](#user-content-spec)
-- [Comment](#user-content-comment)
-- [Key/Value Pair](#user-content-keyvalue-pair)
-- [Keys](#user-content-keys)
-- [String](#user-content-string)
-- [Integer](#user-content-integer)
-- [Float](#user-content-float)
-- [Boolean](#user-content-boolean)
-- [Offset Date-Time](#user-content-offset-date-time)
-- [Local Date-Time](#user-content-local-date-time)
-- [Local Date](#user-content-local-date)
-- [Local Time](#user-content-local-time)
-- [Array](#user-content-array)
-- [Table](#user-content-table)
-- [Inline Table](#user-content-inline-table)
-- [Array of Tables](#user-content-array-of-tables)
-- [Filename Extension](#user-content-filename-extension)
-- [MIME Type](#user-content-mime-type)
-- [ABNF Grammar](#user-content-abnf-grammar)
+- [Spec](#spec)
+- [Comment](#comment)
+- [Key/Value Pair](#keyvalue-pair)
+- [Keys](#keys)
+- [String](#string)
+- [Integer](#integer)
+- [Float](#float)
+- [Boolean](#boolean)
+- [Offset Date-Time](#offset-date-time)
+- [Local Date-Time](#local-date-time)
+- [Local Date](#local-date)
+- [Local Time](#local-time)
+- [Array](#array)
+- [Table](#table)
+- [Inline Table](#inline-table)
+- [Array of Tables](#array-of-tables)
+- [Filename Extension](#filename-extension)
+- [MIME Type](#mime-type)
+- [ABNF Grammar](#abnf-grammar)
 
 Spec
 ----
@@ -75,16 +75,16 @@ key = "value"
 
 Values must have one of the following types.
 
-- [String](#user-content-string)
-- [Integer](#user-content-integer)
-- [Float](#user-content-float)
-- [Boolean](#user-content-boolean)
-- [Offset Date-Time](#user-content-offset-date-time)
-- [Local Date-Time](#user-content-local-date-time)
-- [Local Date](#user-content-local-date)
-- [Local Time](#user-content-local-time)
-- [Array](#user-content-array)
-- [Inline Table](#user-content-inline-table)
+- [String](#string)
+- [Integer](#integer)
+- [Float](#float)
+- [Boolean](#boolean)
+- [Offset Date-Time](#offset-date-time)
+- [Local Date-Time](#local-date-time)
+- [Local Date](#local-date)
+- [Local Time](#local-time)
+- [Array](#array)
+- [Inline Table](#inline-table)
 
 Unspecified values are invalid.
 
@@ -93,7 +93,7 @@ key = # INVALID
 ```
 
 There must be a newline (or EOF) after a key/value pair. (See [Inline
-Table](#user-content-inline-table) for exceptions.)
+Table](#inline-table) for exceptions.)
 
 ```
 first = "Tom" last = "Preston-Werner" # INVALID
@@ -162,7 +162,7 @@ In JSON land, that would give you the following structure:
 ```
 
 For details regarding the tables that dotted keys define, refer to the
-[Table](#user-content-table) section below.
+[Table](#table) section below.
 
 Whitespace around dot-separated parts is ignored. However, best practice is to
 not use any extraneous whitespace.
@@ -667,7 +667,7 @@ key2 = 456
 ```
 
 Naming rules for tables are the same as for keys (see definition of
-[Keys](#user-content-keys) above).
+[Keys](#keys) above).
 
 ```toml
 [dog."tater.man"]