[Dbconfig-common-changes] [dbconfig-common] r217 - in trunk: debian doc

[Sean Finney]

Author: seanius
Date: 2006-05-19 06:16:13 +0000 (Fri, 19 May 2006)
New Revision: 217

Modified:
   trunk/debian/changelog
   trunk/doc/dbapp-policy.sgml
   trunk/doc/dbconfig-common-using.html
   trunk/doc/dbconfig-common.sgml
Log:
spelling fixes

Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog	2006-05-16 01:14:43 UTC (rev 216)
+++ trunk/debian/changelog	2006-05-19 06:16:13 UTC (rev 217)
@@ -1,3 +1,10 @@
+dbconfig-common (1.8.15) UNRELEASED; urgency=low
+
+  * andrew mcmillan found a spelling error, so i ran aspell over all
+    the documentation :)
+
+ -- seanius <seanius at debian.org>  Mon, 15 May 2006 20:08:27 -0500
+
 dbconfig-common (1.8.14) unstable; urgency=low
 
   * temporarily disabling the "dump database before purge" feature,

Modified: trunk/doc/dbapp-policy.sgml
===================================================================
--- trunk/doc/dbapp-policy.sgml	2006-05-16 01:14:43 UTC (rev 216)
+++ trunk/doc/dbapp-policy.sgml	2006-05-19 06:16:13 UTC (rev 217)
@@ -38,7 +38,7 @@
 	databases: <em>persistent</em> and <em>cached</em>.
 
 	<p>
-	<em>Persistant</em> databases contain data that can not be
+	<em>Persistent</em> databases contain data that can not be
 	entirely reconstituted in the case that the database is removed.
 	Also included are databases that if removed would cause serious
 	denial of service (making a system unstable/unusable) or security
@@ -66,7 +66,7 @@
 	<sect id="placement">Placement of databases
 	<p>
 	Both persistent and cached databases fall under already
-	defined guidelines in the FHS; persistant data must be placed
+	defined guidelines in the FHS; persistent data must be placed
 	under <file>/var/lib/packagename</file>, and cached data under
 	<file>/var/cache/packagename</file>, respectively <footnote>or
 	an equivalently compliant location</footnote>.	The remainder
@@ -156,7 +156,7 @@
 	<p>
 	while not essential, a set of common tools for packaging and
 	configuring these applications can make the life of the maintainer
-	as well as the adminsitrator much easier.
+	as well as the administrator much easier.
 
 		<sect1 id="dbc"><package>dbconfig-common</package>
 		<p>

Modified: trunk/doc/dbconfig-common-using.html
===================================================================
--- trunk/doc/dbconfig-common-using.html	2006-05-16 01:14:43 UTC (rev 216)
+++ trunk/doc/dbconfig-common-using.html	2006-05-19 06:16:13 UTC (rev 217)
@@ -212,7 +212,7 @@
 <a name="updates">
 <h4> database changes in new versions of your package </h4>
 <p>
-occassionaly, the upstream authors will modify the underlying databases
+occasionally, the upstream authors will modify the underlying databases
 between versions of their software.  for example, in mysql applications
 column names may change, move to new tables, or the data itself may need
 to be modified in newer upstream versions of a package.
@@ -233,7 +233,7 @@
 where VERSION is the version at which the upgrade should be applied.
 when a package upgrade occurs, all instances of VERSION which are newer
 than the previously installed version will be applied, in order.  there
-is also an automatically included set of safeguards and behaviour provided
+is also an automatically included set of safeguards and behavior provided
 by dbconfig-common, so as the packager you shouldn't need to worry about
 most of the error-handling.
 
@@ -281,7 +281,7 @@
 </pre>
 
 and the config script would contain an additional variable called
-"dbc_dbtypes", which is a comma-seperated list of supported database
+"dbc_dbtypes", which is a comma-separated list of supported database
 types:
 
 <pre>

Modified: trunk/doc/dbconfig-common.sgml
===================================================================
--- trunk/doc/dbconfig-common.sgml	2006-05-16 01:14:43 UTC (rev 216)
+++ trunk/doc/dbconfig-common.sgml	2006-05-19 06:16:13 UTC (rev 217)
@@ -9,7 +9,7 @@
 <abstract>
 	<package>dbconfig-common</package> is an implementation of the "best practices for
 	database applications" draft, which provides debian packagers
-	with an easy, reliable, and consistant method for managing
+	with an easy, reliable, and consistent method for managing
 	databases used by debian packages.
 <copyright>
     Copyright © 2005 sean finney <email>seanius at debian.org</email>.
@@ -41,7 +41,7 @@
 		<item>work for local admins with little effort on
 		their part
 		<item>comply with an agreed upon set of standards for
-		behaviour
+		behavior
 		<item>do absolutely nothing if it is the whim of the
 		local admin
 		<item>perform all operations from within the standard
@@ -257,7 +257,7 @@
 
 		<sect1 id="updates">Database changes in new versions of your package
 			<p>
-			occassionaly, the upstream authors will modify the
+			occasionally, the upstream authors will modify the
 			underlying databases between versions of their
 			software.  for example, in mysql applications
 			column names may change, move to new tables,
@@ -282,7 +282,7 @@
 			<var>VERSION</var> which are newer than the
 			previously installed version will be applied,
 			in order.  there is also an automatically included
-			set of safeguards and behaviour provided by
+			set of safeguards and behavior provided by
 			<package>dbconfig-common</package>, so as the packager you shouldn't
 			need to worry about most of the error-handling.
 
@@ -328,7 +328,7 @@
 
 			<p>
 			The <var>config</var> script would contain an additional variable called
-			"dbc_dbtypes", which is a comma-seperated list of supported database
+			"dbc_dbtypes", which is a comma-separated list of supported database
 			types:
 
 			<p>