svn commit - mysqldoc@docsrva: r4027 - trunk/internals

[mcbrown]

Author: mcbrown
Date: 2006-11-24 05:37:28 +0100 (Fri, 24 Nov 2006)
New Revision: 4027

Log:
Some miniro modifications based on Trudy's comments



Modified:
   trunk/internals/fileformats.xml


Modified: trunk/internals/fileformats.xml
===================================================================
--- trunk/internals/fileformats.xml	2006-11-23 16:04:28 UTC (rev 4026)
+++ trunk/internals/fileformats.xml	2006-11-24 04:37:28 UTC (rev 4027)
Changed blocks: 7, Lines Added: 12, Lines Deleted: 12; 3603 bytes

@@ -20,7 +20,7 @@
       definition). The file bears the same name as the table, with a
       <literal>.frm</literal> extension. The
<literal>.frm</literal>
       format is the same on all platforms but in the description of the
-      .frm format that follows, the examples come from tables created
+      <literal>.frm</literal> format that follows, the examples come from
tables created
       under the Linux operating system.
     </para>
 

@@ -32,7 +32,7 @@
 Query OK, 0 rows affected (0.00 sec)</programlisting>
 
     <para>
-      The <literal>.frm</literal> file associated with table1 can be
+      The <literal>.frm</literal> file associated with
<literal>table1</literal> can be
       located in the directory that represents the database (or schema)
       to which the table belongs. The <literal>datadir</literal>
       variable contains the name of this directory:

@@ -60,9 +60,9 @@
 1 row in set (0.00 sec)</programlisting>
 
     <para>
-      Since MySQL stores .frm files in 'datadir/database_name', it's a
-      simple matter to locate table1's .frm file with the above
-      information. With Linux shell, say:
+      Since MySQL stores <literal>.frm</literal> files in
<filename>datadir/database_name</filename>, it's a
+      simple matter to locate the corresponding <literal>.frm</literal> file
for
+      <literal>table1</literal>. For example, within a Linux shell:
     </para>
 
 <programlisting>shell&gt; su root

@@ -86,7 +86,7 @@
       The <literal>.MYD</literal> and <literal>.MYI</literal>
files are
       not our concern here; they are described elsewhere in this MySQL
       internals manual. To understand the <literal>.frm</literal>
-      format, let's look at table1.frm using a hexadecimal-dump utility;
+      format, let's look at <filename>table1.frm</filename> using a
hexadecimal-dump utility;
       the contents are show below.
     </para>
 

@@ -121,11 +121,11 @@
       details are correct by comparing this description with the
       statements in <filename>sql/table.cc</filename>,
       <literal>create_frm()</literal>. The table below explains the
-      meaning of each byte in the hexadecimal dump shown in Table 1. In
-      Table 2, "Offset" shows the byte position in the file, "Length" is
-      the number of bytes, "Value" is what's in that byte position for
+      meaning of each byte in the hexadecimal dump shown in the above example.
+      The Offset column shows the byte position in the file; Length is
+      the number of bytes; Value is what's in that byte position for
       that length (remember that storage is "low byte first" so 0010
-      means 1000!), and "Explanation" provides a brief explanation of
+      means 1000!); and Explanation provides a brief explanation of
       the contents.
     </para>
 

@@ -505,7 +505,7 @@
 
     <para>
       The <literal>.frm</literal> file for a partitioned table contains
-      partition informatin, in clear text, in addition to the usual
+      partition information, in clear text, in addition to the usual
       table definition details. Let's create a partitioned table and do
       a hexadecimal dump of its <literal>.frm</literal>.
     </para>

@@ -566,7 +566,7 @@
       a view made with:
     </para>
 
-<programlisting>mysql&gt; CREATE VIEW v AS SELECT 5";
+<programlisting>mysql&gt; CREATE VIEW v AS SELECT 5;
 Query OK, 0 rows affected (0.00 sec)</programlisting>
 
     <para>