v0.2.47..v0.2.48 changeset HootenannyServicesDatabaseNotes.asciidoc

diff --git a/docs/developer/HootenannyServicesDatabaseNotes.asciidoc b/docs/developer/HootenannyServicesDatabaseNotes.asciidoc
index 0eb7ace..7953b96 100644
--- a/docs/developer/HootenannyServicesDatabaseNotes.asciidoc
+++ b/docs/developer/HootenannyServicesDatabaseNotes.asciidoc
@@ -14,7 +14,7 @@ Liquibase is used to manage the schema, populate new databases and upgrade/rollb
 * Added any ChangeSet commands for your changes. The `001-Initial.xml` will likely provide some good examples.
 * You must define a context attribute for your changeset.  If the changeset is to be run in any environment (development, production, etc.), use the "default" context.  If you only want the changeset to run in the production environment, use the "production" context, etc.  New contexts may be used if needed.
 * Your ChangeSet should support rolling back. Test if necessary.
-* Update ServicesDb::expectedDbVersion in `$HOOT_HOME/hoot-core/src/main/cpp/hoot/core/io/ServicesDb.h` with the new database version, *only* if the context of the changeset is "default" or some other context meant to be run against the development environment with the unit tests.  
+* Update ServicesDb::expectedDbVersion in `$HOOT_HOME/hoot-core/src/main/cpp/hoot/core/io/ServicesDb.h` with the new database version, *only* if the context of the changeset is "default" or some other context meant to be run against the development environment with the unit tests.
 ** If the last changeset in the set of changesets is meant to run only in a non "default" context ("production", etc.) you will receive warnings from hoot that the "expected db version does not match the actual db version".  As a workaround to avoid this, ensure that the last changeset in the set of changesets always has a "default" context associated with it, even if this means re-ordering your non "default" context changesets to occur earlier in the changesets sequence.  e.g. I add a "production" context changeset meant to only be run in the production environment for the purposes of adding onsite specific data.  The changeset will not run in the development environment and hoot will work properly with no warnings.  In the production environment, a warning will be logged b/c the database version encountered will be one greater than the expected version.  So, swap versions between the newly added "production" context changeset and the most recent "default" context changeset as a workaround.
 
 === Schema