Man pages: consistent spelling of GOTO binary

We sometimes used "goto-binary" or "goto binary." Use "GOTO binary" in
all cases.

Author: tautschnig

doc/man/goto-cc.1

@@ -18,22 +18,22 @@ goto\-cc \- C/C++ to goto compiler
 
 .SH DESCRIPTION
 .B goto\-cc
-reads source code, and generates a goto-binary. Its
+reads source code, and generates a GOTO binary. Its
 command-line interface is designed to mimic that of
 .BR gcc (1).
 Note in particular that \fBgoto-cc\fR distinguishes between compiling
-and linking phases, just as \fBgcc\fR(1) does. \fBcbmc\fR(1) expects a goto-binary
+and linking phases, just as \fBgcc\fR(1) does. \fBcbmc\fR(1) expects a GOTO binary
 for which linking has been completed.
 .PP
 The basename of the file that is used to invoke \fBgoto-cc\fR controls which
 behavior will be emulated. This is typically accomplished by using symbolic
 links.
 .IP
 \fBgoto-cc\fR: invokes the default system compiler as preprocessor and just
-builds a goto-binary.
+builds a GOTO binary.
 .IP
 \fBgoto-gcc\fR: invokes \fBgcc\fR(1) as preprocessor and builds an \fBelf\fR(5)
-object file including an additional \fIgoto-cc\fR section that holds the goto
+object file including an additional \fIgoto-cc\fR section that holds the GOTO
 binary.
 .IP
 \fBgoto-ld\fR: only performs linking, and also builds an \fBelf\fR(5) object as

doc/man/goto-harness.1

@@ -11,7 +11,7 @@ show version
 .TP
 .B goto\-harness \fIin\fB \fIout\fB \-\-harness\-function\-name\ \fIname\fB \-\-harness\-type \fIharness\-type\fR [\fBharness-options\fR]
 build harness for \fIin\fR and write harness to \fIout\fR; the harness is
-printed as C code, if \fIout\fR has a .c suffix, else a goto binary including
+printed as C code, if \fIout\fR has a .c suffix, else a GOTO binary including
 the harness is generated
 .SH DESCRIPTION
 \fBgoto\-harness\fR constructs functions that set up an appropriate environment
@@ -104,7 +104,7 @@ Treat the function parameter with the name \fIp\fR as a string of characters.
 Initialize memory from JSON memory snapshot stored in \fIfile\fR.
 .TP
 \fB\-\-initial\-goto\-location\fR \fIfunc\fR[:\fIn\fR]
-Use function \fIfunc\fR and goto binary location number \fIn\fR as entry point.
+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

doc/man/symtab2gb.1

@@ -1,16 +1,16 @@
 .TH SYMTAB2GB "1" "June 2022" "symtab2gb-5.59.0" "User Commands"
 .SH NAME
-symtab2gb \- Compile JSON symbol tables to a goto binary
+symtab2gb \- Compile JSON symbol tables to a GOTO binary
 .SH SYNOPSIS
 .TP
 .B symtab2gb [\-?] [\-h] [\-\-help]
 show help
 .TP
 .B symtab2gb \fIjson\-symtab\-file\fR+ [\fB\-\-out \fIoutfile\fR]
 compile symbol tables in JSON format
-to a single goto binary
+to a single GOTO binary
 .SH DESCRIPTION
-This utility is to compile a \fBcbmc\fR(1) symbols table (in JSON format) into a goto binary.
+This utility is to compile a \fBcbmc\fR(1) symbols table (in JSON format) into a GOTO binary.
 This is to support integration of external language frontends, such as Ada
 (using GNAT2GOTO: https://github.com/diffblue/gnat2goto) or Rust (using Kani:
 https://github.com/model-checking/kani).