Fix broken named anchor link (#1870)

Prefix the closing angle bracket with a forward slash so that a correct stub is generated for table of contents.

docs/options.md

@@ -185,25 +185,25 @@ Option values:
 - `true` (default) - use unicode flag "u".
 - `false` - do not use flag "u".
 
-### timestamp <Badge text="JTD only">
+### timestamp <Badge text="JTD only" />
 
 Defines which Javascript types will be accepted for the [JTD timestamp type](./json-type-definition#type-form).
 
 By default Ajv will accept both Date objects and [RFC3339](https://datatracker.ietf.org/doc/rfc3339/) strings. You can specify allowed values with the option `timestamp: "date"` or `timestamp: "string"`.
 
-### parseDate <Badge text="JTD only">
+### parseDate <Badge text="JTD only" />
 
 Defines how date-time strings are parsed by [JTD parsers](./api.md#jtd-parse). By default Ajv parses date-time strings as string. Use `parseDate: true` to parse them as Date objects.
 
-### allowDate <Badge text="JTD only">
+### allowDate <Badge text="JTD only" />
 
 Defines how date-time strings are parsed and validated. By default Ajv only allows full date-time strings, as required by JTD specification. Use `allowDate: true` to allow date strings both for validation and for parsing.
 
 ::: warning Option allowDate is not portable
 This option makes JTD validation and parsing more permissive and non-standard. The date strings without time part will be accepted by Ajv, but will be rejected by other JTD validators.
 :::
 
-### int32range <Badge text="JTD only">
+### int32range <Badge text="JTD only" />
 
 Can be used to disable range checking for `int32` and `uint32` types.