Do a bunch of proofreading fixes.

[ibg.git] / about.rst

diff --git a/about.rst b/about.rst
index 32e58f2b31b423c7169e49d92c7244a6eb58284f..ae816b9e731f76c6ae2b40182efc26fb9f97ced1 100644 (file)
--- a/about.rst
+++ b/about.rst
@@ -92,22 +92,22 @@ Presentation and style
 Most of the guide's text appears in this typeface, except where we're using
 words which are part of the Inform system (like ``print``, ``Include``,
 ``VerbLib``) or are extracted from one of our games (like ``bird``,
 Most of the guide's text appears in this typeface, except where we're using
 words which are part of the Inform system (like ``print``, ``Include``,
 ``VerbLib``) or are extracted from one of our games (like ``bird``,

-``nest``, ``top_of_tree``).  Terms in **bold type** are included in the
-glossary -- Appendix G on page 273.  We switch to italic type for a
-placeholder: for example you should read the Inform statement:
+``nest``, ``top_of_tree``).

 
 

-.. parsed-literal::
+.. only:: html

 
 

-   print "*string*";
+   Terms that are included in the :doc:`Glossary <appendices/g>` appear as
+   links to that glossary entry.

 
 

-.. todo::
+.. only:: latex
+
+   Terms that are included in the :doc:`Glossary <appendices/g>` appear in
+   blue italic.  In the PDF version, these are links to the glossary entry.
+
+We switch to italic type for a placeholder: for example you should read the
+Inform statement:

 
 

-   The above will not render correctly in PDF.  In PDF the leading 
-   quotes always appear with at least one backquote.  At the moment, the 
-   best solution I can think up is to have a script fire off after LaTeX 
-   generation to take care of this problem so that when the LaTeX code 
-   is compiled, we'll get the correct glyphs.  At the moment, I don't 
-   know how to make such a script automatically run.
+   :samp:`print "{string}";`

 
 as meaning "display on the player's screen the arbitrary character or
 characters which are represented here by the placeholder *string*".
 
 as meaning "display on the player's screen the arbitrary character or
 characters which are represented here by the placeholder *string*".


@@ -168,7 +168,7 @@ locations:
     A more general list of FAQs about IF authorship, covering both Inform
     and the other main systems.
 
     A more general list of FAQs about IF authorship, covering both Inform
     and the other main systems.
 

-*   news:rec.arts.int-fiction
+*   :newsgroup:`rec.arts.int-fiction`

 
     The Usenet newsgroup for authors of IF, commonly known by the
     abbreviation RAIF.  Here you'll find discussion on IF technology,
 
     The Usenet newsgroup for authors of IF, commonly known by the
     abbreviation RAIF.  Here you'll find discussion on IF technology,


@@ -176,7 +176,7 @@ locations:
     assistance with your own "how do I..." questions (but please, look in
     the manual first).
 
     assistance with your own "how do I..." questions (but please, look in
     the manual first).
 

-*   news:rec.games.int-fiction
+*   :newsgroup:`rec.games.int-fiction`

 
     The complementary newsgroup for IF *players*, often known as RGIF.
 
 
     The complementary newsgroup for IF *players*, often known as RGIF.
 


@@ -234,7 +234,6 @@ eventually of presenting, the Inform text adventure development system.
 
 .. [#play]
    If you feel confused about IF in general or about this distinction
 
 .. [#play]
    If you feel confused about IF in general or about this distinction

-   between writing and playing in particular, try glancing ahead at "Just
-   what is interactive fiction?" on page 13 and at "How to play an IF game"
-   on page 209; also, you may find the Ifaq at
-   http://www.plover.net/~textfire/raiffaq/ifaq/ helpful.
+   between writing and playing in particular, try glancing ahead at
+   :doc:`chapters/01` and at :doc:`appendices/a`; also, you may find the
+   Ifaq at http://www.plover.net/~textfire/raiffaq/ifaq/ helpful.