+1 -1

doc/driver/index.mld

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

+3 -1

doc/json.mld

··· 12 12 13 13 {@json[ 14 14 { 15 15 + "header": "<h1>Module <code><span>Stdlib</span></code><a href=\"../../src/stdlib/stdlib.ml.html\" class=\"source_link\">Source</a></h1>", 15 16 "type": "documentation", 16 17 "uses_katex": false, 17 18 "breadcrumbs": [ 18 19 { 19 19 - "name": "🏠", 20 20 + "name": "Package index", 20 21 "href": "../../../index.html", 21 22 "kind": "leaf-page" 22 23 }, ··· 66 67 67 68 The fields of the JSON are as follows: 68 69 70 70 + - [header] is a string containing HTML for the header of the page. 69 71 - [type] field is either [documentation] or [source]. 70 72 - [uses_katex] is [true] if the page has math entries ([{m ...}] or [{math ...}]). 71 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 489 return 0 490 490 ]} 491 491 492 492 + {4:code_block_tags Code Block Tags} 493 493 + Code blocks may have arbitrary metadata associated with them. This metadata is 494 494 + used, for example, for selecting code blocks when extracting them from a source file via the 495 495 + [odoc extract-code] command. The metadata may also be used by other tools that 496 496 + operate on code blocks, for example, {{!https://github.com/realworldocaml/mdx}mdx}. 497 497 + 498 498 + The metadata follows immediately after the language header, and is a list of tags and bindings, separated by whitespace. Tags are simple 499 499 + keywords, and bindings are key-value pairs separated by an equals sign. If whitespace 500 500 + is needed in keys, values or tags, it should be enclosed in double quotes. For example: 501 501 + 502 502 + {v 503 503 + {@ocaml tag1 "tag 2" key1="value 1" "key 2"="value 2"[ 504 504 + ... code goes here ... 505 505 + ]} 506 506 + v} 507 507 + 492 508 {4:verbatim_blocks Verbatim Blocks} 493 509 494 510 It is possible to write language agnostic code blocks, also called verbatim