# 
# 
# patch "monotone.texi"
#  from [fb344df1b7c625bbc53c26a47554c4ce398a5bf3]
#    to [55108706b1bdcfe1eb8c17883f8a694f9bf57d75]
# 
============================================================
--- monotone.texi	fb344df1b7c625bbc53c26a47554c4ce398a5bf3
+++ monotone.texi	55108706b1bdcfe1eb8c17883f8a694f9bf57d75
@@ -299,7 +299,7 @@
 To make a snapshot of a tree, we begin by writing a special file called
 a @dfn{manifest}. In fact, monotone will write this file for us, but we
 could write it ourselves too. It is just a plain text file, in a
-strucutred but human-readable format used by several parts of monotone.
+structured but human-readable format used by several parts of monotone.
 Each file entry of a manifest binds a specific name, as a full path from
 the root of the workspace, to a specific file ID, as the hash of its
 content.  In this way, the manifest collects together the snapshot of