+1 -1

doc/driver/index.mld

··· 50 Warning: Failed to resolve reference unresolvedroot(parse_coment) Couldn't find "parse_coment" 51 ]} 52 53 - which highlights 54 55 {2 Remapping dependencies} 56

··· 50 Warning: Failed to resolve reference unresolvedroot(parse_coment) Couldn't find "parse_coment" 51 ]} 52 53 + which here is highlighting an error in a reference in `odoc_parser.mli`. 54 55 {2 Remapping dependencies} 56

+3 -1

doc/json.mld

··· 12 13 {@json[ 14 { 0 15 "type": "documentation", 16 "uses_katex": false, 17 "breadcrumbs": [ 18 { 19 - "name": "🏠", 20 "href": "../../../index.html", 21 "kind": "leaf-page" 22 }, ··· 66 67 The fields of the JSON are as follows: 68 0 69 - [type] field is either [documentation] or [source]. 70 - [uses_katex] is [true] if the page has math entries ([{m ...}] or [{math ...}]). 71 - [breadcrumbs] is a list of breadcrumb entries with members [name], [href] and [kind]. If [href] is null then there is no index page at that location in the hierarchy. [kind] is one of

··· 12 13 {@json[ 14 { 15 + "header": "<h1>Module <code><span>Stdlib</span></code><a href=\"../../src/stdlib/stdlib.ml.html\" class=\"source_link\">Source</a></h1>", 16 "type": "documentation", 17 "uses_katex": false, 18 "breadcrumbs": [ 19 { 20 + "name": "Package index", 21 "href": "../../../index.html", 22 "kind": "leaf-page" 23 }, ··· 67 68 The fields of the JSON are as follows: 69 70 + - [header] is a string containing HTML for the header of the page. 71 - [type] field is either [documentation] or [source]. 72 - [uses_katex] is [true] if the page has math entries ([{m ...}] or [{math ...}]). 73 - [breadcrumbs] is a list of breadcrumb entries with members [name], [href] and [kind]. If [href] is null then there is no index page at that location in the hierarchy. [kind] is one of

+16

doc/odoc_for_authors.mld

··· 489 return 0 490 ]} 491 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 492 {4:verbatim_blocks Verbatim Blocks} 493 494 It is possible to write language agnostic code blocks, also called verbatim

··· 489 return 0 490 ]} 491 492 + {4:code_block_tags Code Block Tags} 493 + Code blocks may have arbitrary metadata associated with them. This metadata is 494 + used, for example, for selecting code blocks when extracting them from a source file via the 495 + [odoc extract-code] command. The metadata may also be used by other tools that 496 + operate on code blocks, for example, {{!https://github.com/realworldocaml/mdx}mdx}. 497 + 498 + The metadata follows immediately after the language header, and is a list of tags and bindings, separated by whitespace. Tags are simple 499 + keywords, and bindings are key-value pairs separated by an equals sign. If whitespace 500 + is needed in keys, values or tags, it should be enclosed in double quotes. For example: 501 + 502 + {v 503 + {@ocaml tag1 "tag 2" key1="value 1" "key 2"="value 2"[ 504 + ... code goes here ... 505 + ]} 506 + v} 507 + 508 {4:verbatim_blocks Verbatim Blocks} 509 510 It is possible to write language agnostic code blocks, also called verbatim