--- a/man/lispref/extents.texi	Mon Aug 13 11:19:22 2007 +0200
+++ b/man/lispref/extents.texi	Mon Aug 13 11:20:41 2007 +0200
@@ -94,9 +94,9 @@
 information, @xref{Annotations}.
 
   If an extent has its @code{detachable} property set, it will become
-@dfn{detached} (i.e. no longer in the buffer) when all its text is
+@dfn{detached} (i.e. no longer in the buffer) when all its text its
 deleted.  Otherwise, it will simply shrink down to zero-length and
-sit in the same place in the buffer.  By default, the @code{detachable}
+sit it the same place in the buffer.  By default, the @code{detachable}
 property is set on newly-created extents.  @xref{Detached Extents}.
 
   If an extent has its @code{duplicable} property set, it will be
@@ -286,7 +286,7 @@
 
   The following low-level functions are provided for explicitly
 traversing the extents in a buffer according to the display order.
-These functions are mostly intended for debugging---in normal
+These functions are mostly intended for debugging -- in normal
 operation, you should probably use @code{mapcar-extents} or
 @code{map-extents}, or loop using the @var{before} argument to
 @code{extent-at}, rather than creating a loop using @code{next-extent}.
@@ -778,7 +778,7 @@
   It is possible for an extent's parent to itself have a parent,
 and so on.  Through this, a whole tree of extents can be created,
 all deriving their properties from one root extent.  Note, however,
-that you cannot create an inheritance loop---this is explicitly
+that you cannot create an inheritance loop -- this is explicitly
 disallowed.
 
   Parent extents are used to implement the extents over the modeline.