Small fixes (#749)

I found some issues with the formatting and links, so fixed them up!

modules/ROOT/pages/functions/index.adoc

@@ -155,7 +155,7 @@ These functions return a single value.
 | Converts a value to a `BOOLEAN` value, or null if the value cannot be converted.
 
 1.2+| xref::functions/scalar.adoc#functions-tofloat[`toFloat()`]
-| `toFloat(input :: INTEGER | FLOAT) :: FLOAT`
+| `toFloat(input :: INTEGER \| FLOAT) :: FLOAT`
 | Converts an `INTEGER` value to a `FLOAT` value.
 | `toFloat(input :: STRING) :: FLOAT`
 | Converts a `STRING` value to a `FLOAT` value.
@@ -165,7 +165,7 @@ These functions return a single value.
 | Converts a value to a `FLOAT` value, or null if the value cannot be converted.
 
 1.3+| xref::functions/scalar.adoc#functions-tointeger[`toInteger()`]
-| `toInteger(input :: INTEGER | FLOAT) :: INTEGER`
+| `toInteger(input :: INTEGER \| FLOAT) :: INTEGER`
 | Converts a `FLOAT` value to an `INTEGER` value.
 | `toInteger(input :: BOOLEAN) :: INTEGER`
 | Converts a `BOOLEAN` value to an `INTEGER` value.
@@ -361,9 +361,9 @@ These functions all operate on numerical expressions only, and will return an er
 1.3+| xref::functions/mathematical-numeric.adoc#functions-round[`round()`]
 | `round(input :: FLOAT) :: FLOAT`
 | Returns the value of a number rounded to the nearest `INTEGER`.
-| `round(value :: FLOAT, precision :: INTEGER | FLOAT) :: FLOAT`
+| `round(value :: FLOAT, precision :: INTEGER \| FLOAT) :: FLOAT`
 | Returns the value of a number rounded to the specified precision using rounding mode HALF_UP.
-| `round(value :: FLOAT, precision :: INTEGER | FLOAT, mode :: STRING) :: FLOAT`
+| `round(value :: FLOAT, precision :: INTEGER \| FLOAT, mode :: STRING) :: FLOAT`
 | Returns the value of a number rounded to the specified precision with the specified rounding mode.
 
 1.2+| xref::functions/mathematical-numeric.adoc#functions-sign[`sign()`]
@@ -571,11 +571,11 @@ Values of the xref::values-and-types/temporal.adoc[temporal types] -- `DATE`, `Z
 | Creates a `ZONED DATETIME` instant.
 
 1.1+| xref::functions/temporal/index.adoc#functions-datetime-timestamp[`datetime.fromepoch()`]
-| `datetime.fromepoch(seconds :: INTEGER | FLOAT, nanoseconds :: INTEGER | FLOAT) :: ZONED DATETIME`
+| `datetime.fromepoch(seconds :: INTEGER \| FLOAT, nanoseconds :: INTEGER \| FLOAT) :: ZONED DATETIME`
 | Creates a `ZONED DATETIME` given the seconds and nanoseconds since the start of the epoch.
 
 1.1+| xref::functions/temporal/index.adoc#functions-datetime-timestamp[`datetime.fromepochmillis()`]
-| `datetime.fromepochmillis(milliseconds :: INTEGER | FLOAT) :: ZONED DATETIME`
+| `datetime.fromepochmillis(milliseconds :: INTEGER \| FLOAT) :: ZONED DATETIME`
 | Creates a `ZONED DATETIME` given the milliseconds since the start of the epoch.
 
 1.1+| xref::functions/temporal/index.adoc#functions-datetime-realtime[`datetime.realtime()`]

modules/ROOT/pages/functions/scalar.adoc

@@ -1499,7 +1499,7 @@ With this in mind, the below list contains all supported types (as of Neo4j 5.13
 
 This should be taken into account when relying on the output of the `valueType()` function.
 
-See the xref::syntax/expressions.adoc#type-predicate-expressions[type predicate expression] for an alternative way of testing type values.
+See the xref::values-and-types/type-predicate.adoc[type predicate expression] for an alternative way of testing type values.
 
 
 .+valueType()+

modules/ROOT/pages/values-and-types/property-structural-constructed.adoc

@@ -73,7 +73,7 @@ For more details, see xref::values-and-types/working-with-null.adoc[working with
 
 The table below shows the types and their syntactic synonyms.
 
-These types (and their synonyms) can be used in xref::syntax/expressions.adoc#type-predicate-expressions[type predicate expressions] and in xref::constraints/examples.adoc#constraints-examples-node-property-type[node] and xref::constraints/examples.adoc#constraints-examples-relationship-property-type[relationship] property type constraints.
+These types (and their synonyms) can be used in xref::values-and-types/type-predicate.adoc[type predicate expressions] and in xref::constraints/examples.adoc#constraints-examples-node-property-type[node] and xref::constraints/examples.adoc#constraints-examples-relationship-property-type[relationship] property type constraints.
 They are also returned as a `STRING` value when using the xref::functions/scalar.adoc#functions-valueType[valueType()] function.
 
 However, not all types can be used in all places.
@@ -119,7 +119,7 @@ The type `PROPERTY VALUE` is expanded to a closed dynamic union of all valid pro
 
 For example, given the closed dynamic type `BOOL | LIST<INT> | BOOLEAN | LIST<FLOAT | INT>`, the normalized type would be: `BOOLEAN | LIST<INTEGER | FLOAT>`.
 
-This normalization is run on types used in xref::syntax/expressions.adoc#type-predicate-expressions[type predicate expressions], and in xref::constraints/examples.adoc#constraints-examples-node-property-type[node] and xref::constraints/examples.adoc#constraints-examples-relationship-property-type[relationship] property type constraints.
+This normalization is run on types used in xref::values-and-types/type-predicate.adoc[type predicate expressions], and in xref::constraints/examples.adoc#constraints-examples-node-property-type[node] and xref::constraints/examples.adoc#constraints-examples-relationship-property-type[relationship] property type constraints.
 Type normalization is also used to ensure the consistency of the output for the xref::functions/scalar.adoc#functions-valueType[valueType()] function.
 
 [[ordering-of-types]]