#
#
# patch "monotone.texi"
#  from [5da7aa6c36c10e519b2c6c8918651ec879418efe]
#    to [28d0ecc3984cf339731dbf772a43d948c3d0a47f]
#
============================================================
--- monotone.texi	5da7aa6c36c10e519b2c6c8918651ec879418efe
+++ monotone.texi	28d0ecc3984cf339731dbf772a43d948c3d0a47f
@@ -1186,7 +1186,8 @@ @section Creating a Database
 
 Beth decides to use monotone's built-in database management functionality.
 monotone then expects to find managed database files in a couple of predefined
-places (like f.e. @file{~/.monotone/databases}, this is customizable) and acts
+places (like f.e. @file{~/.monotone/databases} on Unix and 
address@hidden on Windows, this is customizable) and acts
 upon those by knowing only their file or basename from anywhere.
 
 To create a new managed database, Beth issues the @command{mtn db init} command
@@ -10740,7 +10741,8 @@ @subsection User Defaults
 paths for valid monotone databases and outputs details on each one.
 
 The default implementation returns a table with a single entry,
address@hidden/databases}, in the user's home directory.
address@hidden/.monotone/databases} on Unix and 
address@hidden on Windows.
 
 @item get_default_database_alias ()