Description: Address man page warnings by groff
 Thanks, Lintian!
 .
 cbmc (5.84.0-1) unstable; urgency=low
 .
   * New upstream release
   * Includes bugfix for unintentional copy (Closes: #984008)
   * Updated Standards version to 4.6.0 (no changes required)
Author: Michael Tautschnig <mt@debian.org>
Bug-Debian: https://bugs.debian.org/984008

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: <vendor|upstream|other>, <url of original patch>
Bug: <url in upstream bugtracker>
Bug-Debian: https://bugs.debian.org/<bugnumber>
Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber>
Forwarded: <no|not-needed|url proving that it has been forwarded>
Reviewed-By: <name and email of someone who approved the patch>
Last-Update: 2023-06-03

--- cbmc-5.84.0.orig/doc/man/cbmc.1
+++ cbmc-5.84.0/doc/man/cbmc.1
@@ -537,7 +537,7 @@ monotonically.  \fBwall\fR: ISO\-8601 wa
 .SH ENVIRONMENT
 All tools honor the TMPDIR environment variable when generating temporary
 files and directories. Furthermore note that
-the preprocessor used by \fBcbmc\R will use environment variables to locate
+the preprocessor used by \fBcbmc\fR will use environment variables to locate
 header files.
 .SH BUGS
 If you encounter a problem please create an issue at
--- cbmc-5.84.0.orig/doc/man/goto-analyzer.1
+++ cbmc-5.84.0/doc/man/goto-analyzer.1
@@ -307,7 +307,7 @@ on a read.  More precise than this is \f
 element for all of the values.  This is relatively cheap but a lot more precise,
 particularly if used with \fBintervals\fR or \fBset-of-constants\fR.
 \fBup-to-n-elements\fR generalizes \fBsmash\fR by storing abstract objects for
-the first \fIn\fR elements of each array (\fIn\R defaults to \fB10\fR and can be
+the first \fIn\fR elements of each array (\fIn\fR defaults to \fB10\fR and can be
 controlled by \fB\-\-vsd\-array\-max\-elements\fR) and then condensing all other
 elements down to a single abstract object.  This allows reasonably fine-grained
 control over the amount of memory used and can give much more precise results
@@ -389,7 +389,7 @@ Output results in plain text to given fi
 Writes the output as a JSON object to \fIfile_name\fR.
 .TP
 \fB\-\-xml\fR \fIfile_name\fR
-Output results in XML format to \fIfile_name\R.
+Output results in XML format to \fIfile_name\fR.
 .TP
 \fB\-\-dot\fR \fIfile_name\fR
 Writes the output in \fBdot\fR(1) format to \fIfile_name\fR.  This is
--- cbmc-5.84.0.orig/doc/man/goto-harness.1
+++ cbmc-5.84.0/doc/man/goto-harness.1
@@ -106,8 +106,8 @@ Initialize memory from JSON memory snaps
 \fB\-\-initial\-goto\-location\fR \fIfunc\fR[:\fIn\fR]
 Use function \fIfunc\fR and GOTO binary location number \fIn\fR as entry point.
 .TP
-\fB\-\-initial\-source\-location\fR \fIfile\R:\fIn\fR
-Use given file name \fIfile\fR and line number \fIn\R in that file as entry
+\fB\-\-initial\-source\-location\fR \fIfile\fR:\fIn\fR
+Use given file name \fIfile\fR and line number \fIn\fR in that file as entry
 point.
 .TP
 \fB\-\-havoc\-variables\fR \fIvars\fR
--- cbmc-5.84.0.orig/doc/man/janalyzer.1
+++ cbmc-5.84.0/doc/man/janalyzer.1
@@ -142,7 +142,7 @@ Output results in plain text to given fi
 Writes the output as a JSON object to \fIfile_name\fR.
 .TP
 \fB\-\-xml\fR \fIfile_name\fR
-Output results in XML format to \fIfile_name\R.
+Output results in XML format to \fIfile_name\fR.
 .TP
 \fB\-\-dot\fR \fIfile_name\fR
 Writes the output in \fBdot\fR(1) format to \fIfile_name\fR.  This is
