Author: buildbot
Date: Sat Sep 21 09:39:37 2013
New Revision: 879309

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/orientation/decision-making.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Sep 21 09:39:37 2013
@@ -1 +1 @@
-1520431
+1525211

Modified: 
websites/staging/openoffice/trunk/content/orientation/decision-making.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/decision-making.html 
(original)
+++ websites/staging/openoffice/trunk/content/orientation/decision-making.html 
Sat Sep 21 09:39:37 2013
@@ -117,7 +117,7 @@ unnecessary and unproductive.  We have a
 change would be uncontroversial, and the change is reversible, then the 
default approach is to go ahead make the change.</p>
 </li>
 <li>
-<p>Terms that you might related to the above are: <a 
href="http://www.urbandictionary.com/define.php?term=JFDI";>JFDI</a> and 
"assuming lazy consensus".</p>
+<p>Terms that you might need to know related to the above are: <a 
href="http://www.urbandictionary.com/define.php?term=JFDI";>JFDI</a> and 
"assuming lazy consensus".</p>
 </li>
 <li>
 <p>However, there are times where CTR is not appropriate and RTC is used.  
This happens, for example, at the end of a release cycle, when we want to 
carefully review
@@ -125,7 +125,7 @@ changes made to the product, in order to
 on the mailing list.</p>
 </li>
 <li>
-<p>A Committer can also voluntarily invocate a RTC on their own changes.  For 
example the Committer might be considering a change that of greater 
significance.  Maybe he would 
+<p>A Committer can also voluntarily invocate a RTC on their own changes.  For 
example the Committer might be considering a change that is of greater 
significance.  Maybe he would 
 value additional input, or technical review.  Maybe the change is 
controversial or require coordination.  If CTR is not appropriate then one can 
make a proposal and send it to 
 the dev mailing list.  </p>
 </li>


Reply via email to