documentation-guide/en_US getting-files.xml, 1.8, 1.9 module-struct.xml, 1.9, 1.10

[Paul W. Frields (pfrields)]

Author: pfrields

Update of /cvs/docs/documentation-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23023

Modified Files:
	getting-files.xml module-struct.xml 
Log Message:
Add section @id attributes


Index: getting-files.xml
===================================================================
RCS file: /cvs/docs/documentation-guide/en_US/getting-files.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- getting-files.xml	15 Nov 2007 02:06:47 -0000	1.8
+++ getting-files.xml	15 Dec 2007 21:58:16 -0000	1.9
@@ -200,7 +200,7 @@
 	</seglistitem>
       </segmentedlist>
     </section>
-    <section>
+    <section id="sn-file-naming">
       <title>File Names</title>
       <para>Follow these guidelines for naming files to make
 	collaboration and document reuse easy:</para>


Index: module-struct.xml
===================================================================
RCS file: /cvs/docs/documentation-guide/en_US/module-struct.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- module-struct.xml	15 Dec 2007 21:50:02 -0000	1.9
+++ module-struct.xml	15 Dec 2007 21:58:16 -0000	1.10
@@ -307,7 +307,7 @@
 	not work for your document.</para>
     </note>
   </section>
-    <section>
+    <section id="sn-module-adding-targets">
       <title>Adding or Changing Targets</title>
       <para>
         To add a new target and rules, place them at the bottom of the
@@ -383,7 +383,7 @@
 mv /tmp/manifest figs/Manifest-en]]></programlisting>
       </example>
     </section>
-    <section>
+    <section id="sn-adding-docbook-file">
       <title>Adding a New DocBook XML File</title>
       <para>To add a new DocBook XML file to an existing document,
 	follow these steps:</para>
@@ -402,7 +402,7 @@
 	</step>
       </procedure>
     </section>
-    <section>
+    <section id="sn-adding-translation">
       <title>Adding a Translation</title>
       <para>Translations are stored as PO (portable object) files, which
 	the toolchain transforms into translated documents.  Each PO