ronn-format.7 in ronn-ng-0.9.0

- old
+ new

@@ -1,8 +1,8 @@
-.\" generated with Ronn-NG/v0.8.2
-.\" http://github.com/apjanke/ronn-ng/tree/0.8.2
-.TH "RONN\-FORMAT" "7" "December 2018" "Ronn-NG 0.8.2" "Ronn Manual"
+.\" generated with Ronn-NG/v0.9.0
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.0
+.TH "RONN\-FORMAT" "7" "December 2018" "Ronn-NG 0.9.0" "Ronn Manual"
 .SH "NAME"
 \fBronn\-format\fR \- manual authoring format based on Markdown
 .SH "SYNOPSIS"
 .nf
 name(1) \-\- short, single\-sentence description
@@ -83,10 +83,10 @@
 .P
 Section headings should be all uppercase and may not contain inline markup\.
 .SH "INLINE MARKUP"
 Manpages have a limited set of text formatting capabilities\. There\'s basically \fBboldface\fR and \fIitalics\fR (often displayed using \fIunderline\fR)\. Ronn uses the following bits of markdown(7) to accomplish this:
 .TP
-\fB`backticks`\fR (markdown compatible)
+\fB\e`backticks\e`\fR (markdown compatible)
 Code, flags, commands, and noun\-like things; typically displayed in in \fBboldface\fR\. All text included within \fBbackticks\fR is displayed literally; other inline markup is not processed\. HTML output: \fB<code>\fR\.
 .TP
 \fB**double\-stars**\fR (markdown compatible)
 Also displayed in boldface\. Unlike backticks, inline markup is processed\. HTML output: \fB<strong>\fR\.
 .TP