trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dia...@apache.org
Subject svn commit: r911198 - /incubator/trafficserver/site/trunk/docs/admin/preface.htm
Date Wed, 17 Feb 2010 22:27:20 GMT
Author: dianes
Date: Wed Feb 17 22:27:19 2010
New Revision: 911198

URL: http://svn.apache.org/viewvc?rev=911198&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=911198&r1=911197&r2=911198&view=diff
==============================================================================
--- incubator/trafficserver/site/trunk/docs/admin/preface.htm (original)
+++ incubator/trafficserver/site/trunk/docs/admin/preface.htm Wed Feb 17 22:27:19 2010
@@ -7,20 +7,19 @@
 
 <body>
 <h1>Preface</h1>
-<p>This manual describes how to use and configure Traffic Server<sup><font
size="-1"></font></sup>. </p>
-<p>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 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> 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>
   <li><a href="getstart.htm">Chapter 2</a> through <a href="log.htm">Chapter
11</a> provide procedural information about starting, monitoring, configuring, and maintaining
Traffic Server. </li>
-  <li>The <a href="stats.htm">Appendices</a> provide Traffic Server reference
information. </li>
+  <li>The various <a href="stats.htm">Appendices</a> provide Traffic Server
reference information. </li>
   <li>The Troubleshooting <a href="trouble.htm">Appendix</a> discusses
frequently asked questions (FAQs) and provides troubleshooting tips. </li>
   <li>The <a href="Glossary.htm">Glossary</a> defines terminology related
to and used throughout this manual.</li>
 </ul>
 <h2>Who Should Read This Manual</h2>
-<p>This manual is intended for Traffic Server system administrators who configure,
run, and administer Traffic Server systems. To use this manual, you should understand web
proxy caching, TCP/IP network protocols, network administration and management, and the Linux
operating system. </p>
+<p>This manual is written for Traffic Server system administrators who configure, run,
and administer Traffic Server systems. To use this manual, you should understand web proxy
caching, TCP/IP network protocols, network administration and management, and the Linux operating
system. </p>
 <h2>Conventions Used in This Manual </h2>
-<p>This manual uses the following typographic conventions.</p>
+<p>This manual uses the  typographic conventions described below.</p>
 <table width="993" border="1">
   <tr>
     <th width="154" scope="col">Convention</th>
@@ -32,23 +31,23 @@
   </tr>
   <tr>
     <td><strong>bold</strong></td>
-    <td>Represents graphical user interface options and menu names: for example, click
the <strong>Protocols</strong> button.</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>
   </tr>
   <tr>
     <td><pre>monospaced face</pre></td>
-    <td>Represents commands, filenames, file content, and computer input and 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>filename</code>.” </td>
+    <td>Represents variables for which you should substitute a value: for example,
“enter <code><i>filename</i></code>.” </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>Enclose optional command arguments in command syntax. For example: <code>add
<em>pathname</em> [<em>size</em>]</code></td>
   </tr>
   <tr>
     <td>vertical line |</td>
-    <td>Separates value options in command syntax: for example, <code>open tcp|udp
ports <em>o_ports</em></code>.</td>
+    <td>Separates value options in command syntax. For example: <code>open tcp|udp
ports <em>o_ports</em></code> </td>
   </tr>
 </table>
 



Mime
View raw message