# HG changeset patch
# User Pierre-Yves.David@ens-lyon.org
# Date 1342450637 -7200
# Node ID 7ef8ab8c6feadb8a9d9e13af144a17cb23e9a38d
# Parent  f348088d3b3fb64c01592ba942e9b53f20afb06b
some more fix

diff -r f348088d3b3f -r 7ef8ab8c6fea docs/obs-terms.rst
--- a/docs/obs-terms.rst	Mon Jul 16 03:59:39 2012 +0200
+++ b/docs/obs-terms.rst	Mon Jul 16 16:57:17 2012 +0200
@@ -44,7 +44,7 @@
 This is why we usually focus on the **first known precursors**  of the rewritten
 changeset. The same apply for *successors*.
 
-Changeset in *any successors* which are not **Obsolete** are called
+Changeset in *any successors* which are not **obsolete** are called
 **newest successors**..
 
 .. note:: I'm not very happy with this naming scheme and I'm looking for a
@@ -111,7 +111,7 @@
 |                     |                          | of  public changesets.      |
 |                     |                          |                             |
 |                     |                          | Public changeset can't      |
-|                     |                          | be deleted and replace      |. *latecomer* |
+|                     |                          | be deleted and replace      |
 |                     |                          | *latecomer*                 |
 |                     |                          | need to be converted into   |
 |                     |                          | an overlay to this public   |