Issue 4925: Don't use @code inside of @example

@example is already set in monospace font (use @display if you don't
want to change fonts).  This replacement was done mechanically using
the script

    sed -i '/@example *$/,/@end example *$/{s/@code{\(\([^@}]\|@[@{}]\)*\)}/\1/g;s/ \+$//;}' $(git grep -l '^@end example$' Documentation)

so not all replacements are really formatted best.  But overall this
looks like an improvement.

3 files changed, 16 insertions, 16 deletions

diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely
index 7cca8e59af..f5546a790a 100644
--- a/Documentation/notation/changing-defaults.itely
+++ b/Documentation/notation/changing-defaults.itely
@@ -1434,7 +1434,7 @@ existing contexts.  To reposition it above the context called
 @qq{main}, it should be defined like this:
 
 @example
-@code{\new Staff \with @{ alignAboveContext = #"main" @} }
+\new Staff \with @{ alignAboveContext = #"main" @}
 @end example
 
 A similar situation arises when positioning a temporary lyrics
@@ -2764,7 +2764,7 @@ Alternatively, in many cases predefined commands exist to specify the
 direction.  These are of the form
 
 @example
-@code{\xxxUp}, @code{\xxxDown} or @code{\xxxNeutral}
+\xxxUp, \xxxDown or \xxxNeutral
 @end example
 
 @noindent
@@ -4281,7 +4281,7 @@ the collisions to be avoided.
 The syntax of @code{\shape} is
 
 @example
-[-]@code{\shape} @var{displacements} @var{item}
+[-]\shape @var{displacements} @var{item}
 @end example
 
 This will reposition the control-points of @var{item} by the amounts
@@ -4483,7 +4483,7 @@ or a @code{\tweak} of a spanner property.
 The syntax for @code{\alterBroken} is
 
 @example
-[-]@code{\alterBroken} @var{property} @var{values} @var{item}
+[-]\alterBroken @var{property} @var{values} @var{item}
 @end example
 
 The argument @var{values} is a list of values, one for each
diff --git a/Documentation/notation/input.itely b/Documentation/notation/input.itely
index ce33708eac..a23943c16c 100644
--- a/Documentation/notation/input.itely
+++ b/Documentation/notation/input.itely
@@ -1119,9 +1119,9 @@ markup conditionally to header and footer text defined within the
 @code{\paper} block, using the following syntax:
 
 @example
-@code{variable} = @code{\markup} @{
+variable = \markup @{
   @dots{}
-  @code{\on-the-fly}  \@var{procedure}  @var{markup}
+  \on-the-fly  \@var{procedure}  @var{markup}
   @dots{}
 @}
 @end example
@@ -1185,8 +1185,8 @@ Several @code{\on-the-fly} conditions can be combined with an
 @q{and} operation, for example,
 
 @example
-  @code{\on-the-fly \first-page}
-  @code{\on-the-fly \last-page}
+  \on-the-fly \first-page
+  \on-the-fly \last-page
   @code{@{ \markup @dots{} \fromproperty #'header: @dots{} @}}
 @end example
 
@@ -1212,9 +1212,9 @@ as the @code{properties} of the PDF file).  For example, setting the
 this title to the PDF document.
 
 @example
-  @code{\header@{}
-    @code{title = "Symphony I"}
-  @code{@}}
+  \header@{
+    title = "Symphony I"
+  @}
 @end example
 
 If you want to set the title of the printed output to one value, but have the
@@ -1222,10 +1222,10 @@ title property of the PDF to have a different value, you can use
 @code{pdftitle}, as below.
 
 @example
-  @code{\header@{}
-    @code{title = "Symphony I"}
-    @code{pdftitle = "Symphony I by Beethoven"}
-  @code{@}}
+  \header@{
+    title = "Symphony I"
+    pdftitle = "Symphony I by Beethoven"
+  @}
 @end example
 
 The variables @code{title}, @code{subject}, @code{keywords},
diff --git a/Documentation/notation/rhythms.itely b/Documentation/notation/rhythms.itely
index 05d71edc49..704d96e007 100644
--- a/Documentation/notation/rhythms.itely
+++ b/Documentation/notation/rhythms.itely
@@ -1715,7 +1715,7 @@ These are created using the @code{\compoundMeter} function.  The syntax
 for this is:
 
 @example
-\compoundMeter #'@code{(list of lists)}
+\compoundMeter #'(list of lists)
 @end example
 
 The simplest construction is a single list, where the @emph{last} number