2005-09-02 Joel Sherrill <joel@OARcorp.com>

	* FAQ/basic.texi, FAQ/bsp.texi, FAQ/build45.texi, FAQ/concepts.texi,
	FAQ/debug.texi, FAQ/endoftime.texi, FAQ/freesw.texi,
	FAQ/hwdebugaids.texi, FAQ/projects.texi, FAQ/stamp-vti,
	FAQ/tools.texi, FAQ/version.texi, bsp_howto/rtc.t, started/buildc.t,
	started/buildrt.t, user/Makefile.am, user/region.t: Fix typos and
	regenerate.

10 files changed, 31 insertions, 36 deletions

diff --git a/doc/ChangeLog b/doc/ChangeLog
index 51b533e0e8..c2b2e1d2be 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,12 @@
+2005-09-02	Joel Sherrill <joel@OARcorp.com>
+
+	* FAQ/basic.texi, FAQ/bsp.texi, FAQ/build45.texi, FAQ/concepts.texi,
+	FAQ/debug.texi, FAQ/endoftime.texi, FAQ/freesw.texi,
+	FAQ/hwdebugaids.texi, FAQ/projects.texi, FAQ/stamp-vti,
+	FAQ/tools.texi, FAQ/version.texi, bsp_howto/rtc.t, started/buildc.t,
+	started/buildrt.t, user/Makefile.am, user/region.t: Fix typos and
+	regenerate.
+
 2005-06-17	Joel Sherrill <joel@OARcorp.com>
 
 	* user/region.t: Add documentation on region_resize_segment.
diff --git a/doc/FAQ/basic.texi b/doc/FAQ/basic.texi
index 9e8c61d22b..5e48322db5 100644
--- a/doc/FAQ/basic.texi
+++ b/doc/FAQ/basic.texi
@@ -228,21 +228,6 @@ mailing list is archived at:
 http://www.rtems.com/ml/rtems-users
 @end example
 
-The @code{@value{RTEMSSNAPSHOTS}} mailing list is for those
-interested in taking a more active role in the design, development,
-and maintenance of RTEMS.  Discussions on this list tend to focus
-on problems in the development source, design of new features, problem
-reports, etc..  Subscribe by sending an empty mail
-message to @code{@value{RTEMSSNAPSHOTSSUBSCRIBE}}.
-mailing list is archived at:
-
-@example
-http://www.rtems.com/ml/rtems-snapshots
-@end example
-
-The archives for both mailing lists include discussions back
-to 1997.
-
 
 @node Are there any license restrictions?, Are there any export restrictions?, Are there any mailing lists?, Basic Information
 
diff --git a/doc/FAQ/build45.texi b/doc/FAQ/build45.texi
index 507b257803..0912c0af17 100644
--- a/doc/FAQ/build45.texi
+++ b/doc/FAQ/build45.texi
@@ -58,7 +58,7 @@ rtems-users mailing list.
 @item A target (typically cross) C- and (optional) C++-Toolchain.
 @item autoconf/automake (optional, recommended)
 @item Perl (optional, recommended, needed by automake and some tools within RTEMS)
-@item m4 (optional, recommended, needed by autoconf, GNU-m4 preferred)
+@item GNU-m4
 
 @end itemize
 
@@ -110,7 +110,7 @@ supported in RTEMS anymore (@ref{Can I use a non-gcc cross-toolchain?}).
 The sources of all gnutools are available at any
 @uref{ftp://ftp.gnu.org,GNU} mirror.
 Native Linux binaries should come with any Linux distribution.
-Native Cygwin binaries should be available at Cygnus.
+Native Cygwin binaries should be available at @uref{http://www.cygwin.com}.
 
 GNU-Toolchain binaries (gcc, binutils etc.) for Linux and patches required
 to build them from source are available from
@@ -182,7 +182,8 @@ configuration (Cf. @ref{configure --program-[prefix|suffix|transform-name]})
 While running a configure script, you see a message like this:
 @example
 checking for m68k-rtems-gcc... (cached) m68k-rtems-gcc
-checking for C compiler default output... configure: error: C compiler cannot create executables
+checking for C compiler default output... configure: error: C compiler
+cannot create executables
 configure: error: /bin/sh '../../../../rtems-ss-@value{VERSION}/c/make/configure'
 failed for c/make
 @end example
@@ -240,7 +241,7 @@ Host tools are supposed not to be prefixed.
 e.g.: cc, ld, gcc, autoconf, automake, aclocal etc.
 
 If using the pre-built tool binaries provided by the RTEMS project,
-simply prepend @code{@value{RTEMSPREFIX}} to @code{$PATH}.
+simply prepend @code{@value{RTEMSPREFIX}}/bin to @code{$PATH}.
 
 
 @node Can I build RTEMS Canadian Cross?, Building RTEMS is slow, How to set up $PATH?, Issues when building RTEMS
diff --git a/doc/FAQ/stamp-vti b/doc/FAQ/stamp-vti
index dec4095e9b..576aa38173 100644
--- a/doc/FAQ/stamp-vti
+++ b/doc/FAQ/stamp-vti
@@ -1,4 +1,4 @@
-@set UPDATED 31 July 2004
-@set UPDATED-MONTH July 2004
-@set EDITION 4.6.99.1
-@set VERSION 4.6.99.1
+@set UPDATED 5 March 2004
+@set UPDATED-MONTH March 2004
+@set EDITION 4.6.99.2
+@set VERSION 4.6.99.2
diff --git a/doc/FAQ/version.texi b/doc/FAQ/version.texi
index ee10d7c24e..576aa38173 100644
--- a/doc/FAQ/version.texi
+++ b/doc/FAQ/version.texi
@@ -1,4 +1,4 @@
 @set UPDATED 5 March 2004
 @set UPDATED-MONTH March 2004
-@set EDITION 4.6.99.1
-@set VERSION 4.6.99.1
+@set EDITION 4.6.99.2
+@set VERSION 4.6.99.2
diff --git a/doc/bsp_howto/rtc.t b/doc/bsp_howto/rtc.t
index 210e3de053..a5844e3d67 100644
--- a/doc/bsp_howto/rtc.t
+++ b/doc/bsp_howto/rtc.t
@@ -48,8 +48,8 @@ the DMV177's @code{RTC_Table} configuration table is below:
 
 boolean dmv177_icm7170_probe(int minor);
 
-rtc_tbl	RTC_Table[] = {
-  { "/dev/rtc0",                /* sDeviceName */
+rtc_tbl	RTC_Table[] = @{
+  @{ "/dev/rtc0",                /* sDeviceName */
     RTC_ICM7170,                /* deviceType */
     &icm7170_fns,               /* pDeviceFns */
     dmv177_icm7170_probe,       /* deviceProbe */
@@ -58,14 +58,14 @@ rtc_tbl	RTC_Table[] = {
     0,                          /* ulDataPort */
     icm7170_get_register_8,     /* getRegister */
     icm7170_set_register_8,     /* setRegister */
-  }
-};
+  @}
+@};
 
 unsigned long  RTC_Count = (sizeof(RTC_Table)/sizeof(rtc_tbl));
 rtems_device_minor_number  RTC_Minor;
 
 boolean dmv177_icm7170_probe(int minor)
-{
+@{
   volatile unsigned16 *card_resource_reg;
 
   card_resource_reg = (volatile unsigned16 *) DMV170_CARD_RESORCE_REG;
@@ -73,7 +73,7 @@ boolean dmv177_icm7170_probe(int minor)
   if ( (*card_resource_reg & DMV170_RTC_INST_MASK) == DMV170_RTC_INSTALLED )
     return TRUE;
   return FALSE;
-}
+@}
 
 @end example
 
diff --git a/doc/started/buildc.t b/doc/started/buildc.t
index f6eaa67349..580a60bda8 100644
--- a/doc/started/buildc.t
+++ b/doc/started/buildc.t
@@ -503,7 +503,7 @@ containing the executables is the prefix used above with
 @file{bin} post-fixed.
 
 @example
-export PATH=@value{RTEMSPREFIX}/bin:${PATH}
+export PATH=@value{RTEMSPREFIX}/bin:$@{PATH@}
 @end example
 
 Failure to have the binutils in the path will cause the GCC and NEWLIB
diff --git a/doc/started/buildrt.t b/doc/started/buildrt.t
index 93df0db738..5ced49cd89 100644
--- a/doc/started/buildrt.t
+++ b/doc/started/buildrt.t
@@ -57,7 +57,7 @@ tools.  The following command prepends the directory
 where the tools were installed in a previous step:
 
 @example
-export PATH=<INSTALL_POINT>/bin:${PATH}
+export PATH=<INSTALL_POINT>/bin:$@{PATH@}
 @end example
 
 NOTE:  The above command is in Bourne shell (@code{sh}) syntax and
diff --git a/doc/user/Makefile.am b/doc/user/Makefile.am
index 1869ef34b1..e2a41671c5 100644
--- a/doc/user/Makefile.am
+++ b/doc/user/Makefile.am
@@ -111,7 +111,7 @@ region.texi: region.t
 
 dpmem.texi: dpmem.t
 	$(BMENU2) \
-	  -p "Region Manager REGION_GET_SEGMENT_SIZE - Obtain size of a segment" \
+	  -p "Region Manager REGION_RESIZE_SEGMENT - Change size of a segment" \
 	    -u "Top" \
 	    -n "I/O Manager" < $< > $@
 
diff --git a/doc/user/region.t b/doc/user/region.t
index b11cf1c2ae..088abe78b5 100644
--- a/doc/user/region.t
+++ b/doc/user/region.t
@@ -719,13 +719,13 @@ procedure Region_Resize_Segment (
 @subheading DESCRIPTION:
 
 This directive is used to increase or decrease the size of 
-a @a{segment}.  When increasing the size of a segment, it
+a segment.  When increasing the size of a segment, it
 is possible that there is not memory available contiguous
 to the segment.  In this case, the request is unsatisfied.
 
 @subheading NOTES:
 
-If an attempt to increase the size of a @a{segment} fails, then
+If an attempt to increase the size of a segment fails, then
 the application may want to allocate a new segment of the desired
 size, copy the contents of the original segment to the new, larger
 segment and then return the original segment.