From ab1969b0150fc5a171f6fe5f6dcd0b545d1f403f Mon Sep 17 00:00:00 2001
From: Drew DeVault <sir@cmpwn.com>
Date: Sun, 20 Jan 2019 10:18:30 -0500
Subject: [PATCH] Add CONVENTIONS to scdoc(5)

---
 scdoc.5.scd | 23 ++++++++++++++---------

diff --git a/scdoc.5.scd b/scdoc.5.scd
index 42c1ec06c3c229afd44fe85b159de0e34c6fc3f3..ab641a77169b8fd36f2a6e2e35f32e05adb25455 100644
--- a/scdoc.5.scd
+++ b/scdoc.5.scd
@@ -14,12 +14,12 @@ Each scdoc file must begin with the following preamble:
 
 	*name*(_section_) ["left\_footer" ["center\_header"]]
 
-*name* is the name of the man page you are writing, and _section_ is the
-section you're writing for (see *man*(1) for information on manual sections).
+*name* is the name of the man page you are writing, and _section_ is the section
+you're writing for (see *man*(1) for information on manual sections).
 
 _left\_footer_ and _center\_header_ are optional arguments which set the text
-positioned at those locations in the generated man page, and *must* be surrounded
-with double quotes.
+positioned at those locations in the generated man page, and *must* be
+surrounded with double quotes.
 
 ## SECTION HEADERS
 
@@ -118,10 +118,10 @@
 To begin a table, add an empty line followed by any number of rows.
 
 Each line of a table should start with | or : to start a new row or column
-respectively, followed by [ or - or ] to align the contents to the left,
-center, or right, followed by a space and the contents of that cell.  You may
-use a space instead of an alignment specifier to inherit the alignment of the
-same column in the previous row.
+respectively, followed by [ or - or ] to align the contents to the left, center,
+or right, followed by a space and the contents of that cell.  You may use a
+space instead of an alignment specifier to inherit the alignment of the same
+column in the previous row.
 
 The first character of the first row is not limited to | and has special
 meaning. [ will produce a table with borders around each cell. | will produce a
@@ -168,7 +168,8 @@
 These blocks will be indented one level. Note that literal text is shown
 literally in the man viewer - that is, it's not a means for inserting your own
 roff macros into the output. Note that \\ is still interpreted within literal
-blocks, which for example can be useful to output \``` inside of a literal block.
+blocks, which for example can be useful to output \``` inside of a literal
+block.
 
 ## COMMENTS
 
@@ -177,6 +178,10 @@
 ```
 ; This is a comment
 ```
+
+# CONVENTIONS
+
+By convention, all scdoc documents should be hard wrapped at 80 columns.
 
 # SEE ALSO
 

-- 
2.48.1