You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by di...@apache.org on 2010/02/19 19:34:30 UTC

svn commit: r911896 - /incubator/trafficserver/site/trunk/docs/admin/preface.htm

Author: dianes
Date: Fri Feb 19 18:34:30 2010
New Revision: 911896

URL: http://svn.apache.org/viewvc?rev=911896&view=rev
Log: (empty)

Modified:
    incubator/trafficserver/site/trunk/docs/admin/preface.htm

Modified: incubator/trafficserver/site/trunk/docs/admin/preface.htm
URL: http://svn.apache.org/viewvc/incubator/trafficserver/site/trunk/docs/admin/preface.htm?rev=911896&r1=911895&r2=911896&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/preface.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/preface.htm Fri Feb 19 18:34:30 2010
@@ -7,7 +7,7 @@
 
 <body>
 <h1>Preface</h1>
-<p>This manual describes how to use and configure Traffic Server<sup><font size="-1"></font></sup>. For information about installing Traffic Server, refer to the <em>Traffic Server Installation Guide</em>. For information about unsupported features and last-minute information not available in this manual, refer to the <em>Release Notes</em>.</p>
+<p>This manual describes how to use and configure Traffic Server<sup><font size="-1"></font></sup>. For information about installing Traffic Server, refer to the <em>Traffic Server SDK Programmer's Guide</em>. For information about unsupported features and last-minute information not available in this manual, refer to the <em>Release Notes</em>.</p>
 <p> The <i>Traffic Server Administrator's Guide</i> covers the following topics: </p>
 <ul>
   <li><a href="intro.htm">Chapter 1</a> provides an overview of Traffic Server features and components. </li>
@@ -27,23 +27,29 @@
   </tr>
   <tr>
     <td><em>italic</em></td>
-    <td>Represents emphasis and introduces terms: for example, “the <em>reverse proxy</em> option.”   </td>
+    <td>Used for emphasis; occasionally used to introduce terms. For example: “the <em>reverse proxy</em> option is used when...”  </td>
   </tr>
   <tr>
+    <td><u>underline</u></td>
+    <td>Used for emphasis. For example: “This means that a new log file will <u>not</u> be created."</td>
+  </tr>
+  
+  <tr>
     <td><strong>bold</strong></td>
-    <td>Represents graphical user interface options and menu names: for example, click the <strong>Protocols</strong> button. Also used to denote glossary or index terms.</td>
+    <td><p>Represents graphical user interface options and menu names. For example: &quot;Click the <strong>Protocols</strong> button.&quot; <br/>
+    Also used to denote glossary or index terms, which may be hyperlinked to another section of the document.</p></td>
   </tr>
   <tr>
     <td><pre>monospaced face</pre></td>
-    <td>Represents commands, filenames, file content, and computer input/output: for example, “use the <code>reconfigure</code> command.”</td>
+    <td>Represents commands, filenames, file content, and computer input/output. For example: “use the <code>reconfigure</code> command.”</td>
   </tr>
   <tr>
     <td><pre><em>monospaced italic</em></pre></td>
-    <td>Represents variables for which you should substitute a value: for example, “enter <code><i>filename</i></code>.” </td>
+    <td>Represents variables for which you should substitute a value. For example: “enter <code><i>filename</i></code> in the appropriate directory.” </td>
   </tr>
   <tr>
     <td>brackets [ ]</td>
-    <td>Enclose optional command arguments in command syntax. For example: <code>add <em>pathname</em> [<em>size</em>]</code></td>
+    <td>Encloses optional command arguments in command syntax. For example: <code>add <em>pathname</em> [<em>size</em>]</code></td>
   </tr>
   <tr>
     <td>vertical line |</td>