Skip to content

Commit f3c7377

Browse files
committed
Revise the infostring description
The infostring sentence uses an inverted construction ("Following the opening fence may be an infostring"); it's a bit awkward. Let's use active voice and tighten the phrasing.
1 parent 32535a2 commit f3c7377

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/frontmatter.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ r[frontmatter.fence]
5757
Frontmatter must start and end with a *fence*. Each fence must start at the beginning of a line. The opening fence must consist of at least 3 and no more than 255 hyphens (`-`). The closing fence must have exactly the same number of hyphens as the opening fence. The hyphens of either fence may be followed by horizontal whitespace.
5858

5959
r[frontmatter.infostring]
60-
Following the opening fence may be an infostring for identifying the intention of the contained content. An infostring may be followed by horizontal whitespace.
60+
The opening fence, after optional horizontal whitespace, may be followed by an infostring that identifies the format or purpose of the body. An infostring may be followed by horizontal whitespace.
6161

6262
r[frontmatter.body]
6363
The body of the frontmatter may contain any content except for a line starting with as many or more hyphens (`-`) than in the fences or carriage returns.

0 commit comments

Comments
 (0)