# 
# 
# patch "ChangeLog"
#  from [f2178a90efaca6bdec0fa7ae7d78693a89fcffd1]
#    to [9008f4ad88501fa734287bdce53a3f5ab9c76712]
# 
# patch "monotone.texi"
#  from [388b671ef779121ddcee6cd3944fc26db4c37b5d]
#    to [c61765ae78e4e832ed9c6bac2daf8e4dea675e1d]
# 
============================================================
--- ChangeLog	f2178a90efaca6bdec0fa7ae7d78693a89fcffd1
+++ ChangeLog	9008f4ad88501fa734287bdce53a3f5ab9c76712
@@ -1,3 +1,8 @@
+2006-04-27  Daniel Carosone  <address@hidden>
+	* monotone.texi: add a missing $ to a packet example, and an
+	introductory paragraph to the section. From Jeronimo Pellegrini,
+	with minor wording tweaks.
+
 2006-04-27  Alex Queiroz  <address@hidden>
 
 	* po/pt_BR.po: Translated more strings.
============================================================
--- monotone.texi	388b671ef779121ddcee6cd3944fc26db4c37b5d
+++ monotone.texi	c61765ae78e4e832ed9c6bac2daf8e4dea675e1d
@@ -3372,9 +3372,17 @@
 @node    Using packets
 @section Using packets
 
+Suppose you made changes to your database, and want to send those
+changes to someone else but for some reason you cannot use netsync.  Or
+maybe you want to extract and inject individual revisions automatically
+via an external program. In this case, you can convert the information
+into packets. Packets are a convenient way to represent revisions and
+other database contents as plain text with wrapped lines -- just what
+you need if you want to send them in the body of an email.
+
 This is a tutorial on how to transfer single revisions between
 databases by dumping them from one database to a text file and then
-reading the dump in a second database.
+reading the dump into a second database.
 
 We will create two databases, A and B, then create a few revisions in
 A, and transfer part of them to B.
@@ -3543,7 +3551,7 @@
 $ mtn -d B co -b test test-B
 $ ls test-B
 file2  _MTN  x
-more test-B/file2
+$ more test-B/file2
 file 2 getting in
 @end group
 @end smallexample