.\" Complete independent document; no previous example is required.
.nr PO .5i
.nr LL 4.7i
.nr LT 4.7i
.nr HM .55i
.nr FM .55i
.nr PS 10
.nr VS 13
.ds RH GRF-05-002
.if n .ftr CR R
.pl 8.2677i
.\" BEGIN EXAMPLE
.TL
A two-column bulletin
.2C
.NH 1
Input
.PP
A short column can carry a compact explanation of the data and its source.
.PP
Keep paragraphs concise when the line measure is narrow.
.NH 1
Output
.PP
The formatter fills the first column before advancing to the next one.
.PP
The output device determines how the same source is rendered. PDF preserves page geometry, while terminal text uses a fixed character grid.
.NH 1
Review
.PP
Read the source before reviewing the page. A heading should describe the following material, and an example should match the interface it explains. Keep explanations near the commands and values that readers will need.
.PP
Review the generated PDF at a comfortable scale. Check the beginning and end of each column, line lengths, captions and page numbers. A successful compilation is useful evidence, but it cannot determine whether the text answers the reader's question.
.PP
Inspect terminal output separately. Tables may need a narrower format, and diagrams may need a text alternative. Do not assume that a drawing designed for paper can be reproduced accurately on a character grid.
.PP
When preparing a release, keep the original source and the exact formatting command together. Record the macro package and any required preprocessor. This makes the document easier to rebuild and gives future maintainers a clear place to start.
.PP
In a longer report, the column flow continues across page boundaries. Here, a short conclusion deliberately returns to full width on the next page.
.1C
.NH 1
Conclusion
.PP
The full-width discussion resumes after leaving the column layout.
.\" END EXAMPLE
.br
.sp .4v
.nf
.ps 7
\f[CR]GRF-05-002\f[]
.fi