Fix relative links

Author: Fokko

doc/content/en/docs/1.11.1/IDL Language/_index.md

@@ -170,10 +170,10 @@ The primitive types supported by Avro IDL are the same as those supported by Avr
 ### Logical Types
 Some of the logical types supported by Avro's JSON format are also supported by Avro IDL. The currently supported types are:
 
-* _decimal_ (logical type [decimal]({{< relref "specification#decimal" >}}))
-* _date_ (logical type [date]({{< relref "specification#date" >}}))
-* _time_ms_ (logical type [time-millis]({{< relref "specification#time-millisecond-precision" >}}))
-* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "specification#timestamp-millisecond-precision" >}}))
+* _decimal_ (logical type [decimal]({{< relref "../specification#decimal" >}}))
+* _date_ (logical type [date]({{< relref "../specification#date" >}}))
+* _time_ms_ (logical type [time-millis]({{< relref "../specification#time-millisecond-precision" >}}))
+* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "../specification#timestamp-millisecond-precision" >}}))
 
 For example:
 ```java
@@ -206,7 +206,7 @@ record Card {
 ``` 
 
 ### Default Values
-Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "specification#schema-record" >}}).
+Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "../specification#schema-record" >}}).
 
 ### Complex Types
 

doc/content/en/docs/1.11.2/IDL Language/_index.md

@@ -170,11 +170,11 @@ The primitive types supported by Avro IDL are the same as those supported by Avr
 ### Logical Types
 Some of the logical types supported by Avro's JSON format are also supported by Avro IDL. The currently supported types are:
 
-* _decimal_ (logical type [decimal]({{< relref "specification#decimal" >}}))
-* _date_ (logical type [date]({{< relref "specification#date" >}}))
-* _time_ms_ (logical type [time-millis]({{< relref "specification#time-millisecond-precision" >}}))
-* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "specification#timestamp-millisecond-precision" >}}))
-* _uuid_ (logical type [uuid]({{< relref "specification#uuid" >}}))
+* _decimal_ (logical type [decimal]({{< relref "../specification#decimal" >}}))
+* _date_ (logical type [date]({{< relref "../specification#date" >}}))
+* _time_ms_ (logical type [time-millis]({{< relref "../specification#time-millisecond-precision" >}}))
+* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "../specification#timestamp-millisecond-precision" >}}))
+* _uuid_ (logical type [uuid]({{< relref "../specification#uuid" >}}))
 
 For example:
 ```java
@@ -208,7 +208,7 @@ record Card {
 ```
 
 ### Default Values
-Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "specification#schema-record" >}}).
+Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "../specification#schema-record" >}}).
 
 ### Complex Types
 

doc/content/en/docs/1.11.3/IDL Language/_index.md

@@ -170,11 +170,11 @@ The primitive types supported by Avro IDL are the same as those supported by Avr
 ### Logical Types
 Some of the logical types supported by Avro's JSON format are also supported by Avro IDL. The currently supported types are:
 
-* _decimal_ (logical type [decimal]({{< relref "specification#decimal" >}}))
-* _date_ (logical type [date]({{< relref "specification#date" >}}))
-* _time_ms_ (logical type [time-millis]({{< relref "specification#time-millisecond-precision" >}}))
-* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "specification#timestamp-millisecond-precision" >}}))
-* _uuid_ (logical type [uuid]({{< relref "specification#uuid" >}}))
+* _decimal_ (logical type [decimal]({{< relref "../specification#decimal" >}}))
+* _date_ (logical type [date]({{< relref "../specification#date" >}}))
+* _time_ms_ (logical type [time-millis]({{< relref "../specification#time-millisecond-precision" >}}))
+* _timestamp_ms_ (logical type [timestamp-millis]({{< relref "../specification#timestamp-millisecond-precision" >}}))
+* _uuid_ (logical type [uuid]({{< relref "../specification#uuid" >}}))
 
 For example:
 ```java
@@ -208,7 +208,7 @@ record Card {
 ```
 
 ### Default Values
-Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "specification#schema-record" >}}).
+Default values for fields may be optionally specified by using an equals sign after the field name followed by a JSON expression indicating the default value. This JSON is interpreted as described in the [spec]({{< relref "../specification#schema-record" >}}).
 
 ### Complex Types