Remove leftover `` used to keep MoinMoin from making words into WikiLinks

Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

1 files changed, 6 insertions, 6 deletions

diff --git a/XorgTesting.mdwn b/XorgTesting.mdwn
index 4b57235c..39450853 100644
--- a/XorgTesting.mdwn
+++ b/XorgTesting.mdwn
@@ -37,8 +37,8 @@ Note that some systems do not have a compatible version of Freetype2 installed o
 Each of the following install tests can be performed by building the release (as described above using the _sample_ or _alternate_ host.def file provided), running `make Install >& Install.LOG` (or other such command as appropriate for your platform), and checking the Install.LOG output for any failures.
 
 1. Build and install with no host.def file ([[sample|http://www.freedesktop.org/~kem/install-tests/1/host.def]] [[alternate|http://www.freedesktop.org/~kem/install-tests/1a/host.def]])
-1. Build and install with: Project``Root defined to be something other than the default, and Nothing``Outside``Project``Root defined as YES ([[sample|http://www.freedesktop.org/~kem/install-tests/2/host.def]] [[alternate|http://www.freedesktop.org/~kem/install-tests/2a/host.def]])
-Note that some systems do not have a compatible version of Freetype2 installed on their system, so in addition to each install requirement above, defining Has``Freetype2 as NO is permitted.  Each _alternate_ host.def file above have this define included.
+1. Build and install with: ProjectRoot defined to be something other than the default, and NothingOutsideProjectRoot defined as YES ([[sample|http://www.freedesktop.org/~kem/install-tests/2/host.def]] [[alternate|http://www.freedesktop.org/~kem/install-tests/2a/host.def]])
+Note that some systems do not have a compatible version of Freetype2 installed on their system, so in addition to each install requirement above, defining HasFreetype2 as NO is permitted.  Each _alternate_ host.def file above have this define included.
 
 
 ### Conformance tests
@@ -67,14 +67,14 @@ Here are some examples of how to use xreg to run the X test suite:
 1. `xreg -xtest -xorg -d 16`
     * This runs xtest at depth 16 using the Xorg server.
 1. `xreg -xtest -xvfb -d 15 -test XCopyArea`
-    * This runs xtest at depth 15 using the Xvfb server, but it only runs the XCopy``Area test.
+    * This runs xtest at depth 15 using the Xvfb server, but it only runs the XCopyArea test.
     * Selecting individual tests is very useful to track down test failures.
 1. `xreg -xtest -xvfb -d 16 -xvfbwidth 1280 -xvfbheight 1024 -test XFillRectangles -n 3-5`
-    * This runs xtest at depth 16 using the Xvfb server running at 1280x1024, but only runs the third through the fifth tests of the XFill``Rectangles test.
+    * This runs xtest at depth 16 using the Xvfb server running at 1280x1024, but only runs the third through the fifth tests of the XFillRectangles test.
 Notes on using xreg:
 
  * The output from these test runs are stored in `pwd`/results by default.  You can change the default output dir using the -O command line option.
- * The material below assumes that you have done a full install of the system to /usr/X11``R6.  However, if you are using a different Project``Root, you can use the following command line option to the xreg script to run from that alternate location: `-projroot` _path-to-your-project-root_
+ * The material below assumes that you have done a full install of the system to /usr/X11R6.  However, if you are using a different ProjectRoot, you can use the following command line option to the xreg script to run from that alternate location: `-projroot` _path-to-your-project-root_
  * The files that are generated from an xreg run of xtest are:
    1. `X-setup..output` -- this file contains the output of the X server during the setup phase
    1. `xtest.DEPTH.DATE.TIME.errors` -- this file contains the list of errors found during the test run at depth _DEPTH_ made on date _DATE_ at time _TIME_.
@@ -82,7 +82,7 @@ Notes on using xreg:
    1. `xtest.DEPTH.DATE.TIME.summary` -- this file contains a summary of the errors found during the test run at depth _DEPTH_ made on date _DATE_ at time _TIME_.  The summary file is only useful during full test runs (e.g., not when running individual tests).
    1. `xtest.DEPTH.DATE.TIME.results` -- this directory contains the journal from the tests run at depth _DEPTH_ made on date _DATE_ at time _TIME_ as well as any error images generated.
  * After running xtest, you can check to see if everything passed by looking at the summary/errors/report file(s) to see if there are any failures.
- * There are some known failures that the summary file attempts to take into account.  The first part of the summary file is the list of failures, and at the end of the summary file is a diff between the known failures (e.g., XDraw``Arcs) and what the failures were for this run.
+ * There are some known failures that the summary file attempts to take into account.  The first part of the summary file is the list of failures, and at the end of the summary file is a diff between the known failures (e.g., XDrawArcs) and what the failures were for this run.
  * The xreg script has only been tested on Linux systems.  If there are problems with these scripts, please post patches to the [[xorg@lists.freedesktop.org|mailto:xorg@lists.freedesktop.org]] mailing list.
  * There are many other options to xreg (and it can be used to run other tests such as x11perf).  Run `xreg -help` to see the usage message.