Minor fixes in define and include opcode pages

docs/opcodes/define.md

@@ -29,13 +29,22 @@ change key maps, MIDI CC assignments, pitch bend ranges etc. which can then be
 used repeatedly in the SFZ file, but can be easily changed just by editing their
 `#define` value in one place.
 
-Using #define as a constant with a single value thorughout an instrument works
-easily. Defining the same variable to have multiple values at different points in the
-same instrument, however, requires care. Using #define to set the same variable to
-different values at one point in the same SFZ file does not work well at least in
-ARIA/Sforzando when loading an instrument. However, a workaround there is to
-use [#include] to put each set of #define statements with different
-values in a separate file.  In simple tests, that has been successful.
+Using `#define` as a constant with a single value thorughout an instrument works
+easily. Defining the same variable to have multiple values at different points
+in the same instrument, however, requires care.
+
+The following does not work well in ARIA/Sforzando, assuming that B.sfz uses `MYVAR`:
+
+```sfz
+#define MYVAR cc12
+#include B.sfz
+#define MYVAR cc13
+#include B.sfz
+```
+
+However, a workaround there is to use [#include] to put each set of `#define`
+statement with different values in a separate file.
+In simple tests, that has been successful.
 
 
 [#include]: include.md

docs/opcodes/include.md

@@ -66,12 +66,22 @@ tune_cc55=-250
 #include "mappings/bobobo_tenor_l_2.sfz"
 ```
 
-Using #include with [#define] in the same instrument requires care,
+Using `#include` with [#define] in the same instrument requires care,
 especially if the same value has to be #defined to have different settings at
-different points in an instrument. Using #define to set the same variable to different
-values at one point in the same SFZ file does not work well at least in ARIA/Sforzando
-when loading an instrument. However, a workaround there is to use #include to put each
-#define statement in a separate file. In simple tests, that has been successful.
+different points in an instrument.
+
+The following does not work well in ARIA/Sforzando, assuming that B.sfz uses `MYVAR`:
+
+```sfz
+#define MYVAR cc12
+#include B.sfz
+#define MYVAR cc13
+#include B.sfz
+```
+
+However, a workaround there is to use `#include` to put each `#define` statement
+in a separate file.
+In simple tests, that has been successful.
 
 
 [#define]: define.md