subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stef...@apache.org
Subject svn commit: r1582121 - /subversion/site/publish/docs/release-notes/1.9.html
Date Wed, 26 Mar 2014 23:37:00 GMT
Author: stefan2
Date: Wed Mar 26 23:37:00 2014
New Revision: 1582121

URL: http://svn.apache.org/r1582121
Log:
* publish/docs/release-notes/1.9.html
  (): Fix a gazillion typos in the upcoming 1.9 release notes.

Modified:
    subversion/site/publish/docs/release-notes/1.9.html

Modified: subversion/site/publish/docs/release-notes/1.9.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.9.html?rev=1582121&r1=1582120&r2=1582121&view=diff
==============================================================================
--- subversion/site/publish/docs/release-notes/1.9.html (original)
+++ subversion/site/publish/docs/release-notes/1.9.html Wed Mar 26 23:37:00 2014
@@ -339,7 +339,7 @@ deltification.</p>
 
 <p>If you don't want Subversion 1.9 to deltify properties and directories in
 older format repositories, modify or add the following settings in the
-respository's fsfs.conf file:
+repository’s fsfs.conf file:
 </p>
 
 <pre>
@@ -366,7 +366,7 @@ means more net speed, some changes may a
       opt-in.</li>
   <li>Directories 4x as large as in 1.8 can now be cached.</li>
   <li>Caching is quasi-perfect on short time scales (requesting data equal or
-      less than approx. 10% of the cache size).  This greately improves
+      less than approx. 10% of the cache size).  This greatly improves
       performance when e.g. many clients check out the same project.</li>
   <li>Long-term caching is now priority-based with text deltas having the lowest
       priority.  This results in slower but more reliable heating up, i.e. it
@@ -415,7 +415,7 @@ these limitations.  Here some of the int
 <p>Development of FSX has been started as a fork of FSFS to guarantee
 functional completeness and testability.  The current code still contains
 remnants of FSFS legacy code and not all of the above improvements have been
-implemented, yet.  Later releases will close the gap and remove trasitional
+implemented, yet.  Later releases will close the gap and remove transitional
 code.
 </p>
 
@@ -427,9 +427,9 @@ code.
 
 </div>  <!-- fsx-overview -->
 
-<div class="h4" id="fsx-usage-scennarios">
-<h4>Usage scennarios
-  <a class="sectionlink" href="#fsx-usage-scennarios"
+<div class="h4" id="fsx-usage-scenarios">
+<h4>Usage scenarios
+  <a class="sectionlink" href="#fsx-usage-scenarios"
     title="Link to this section">&para;</a>
 </h4>
 
@@ -438,7 +438,7 @@ be no support for 1.9-style FSX reposito
 (see <a href="#fsx-incompatibility">Incompatibility</a>).  Think, therefore,
 of all data in a FSX repository as being potentially corrupt.  Due to its
 superior performance and storage efficiency, however, there are two use-cases
-where FSX might be a vaiable option:</p>
+where FSX might be a viable option:</p>
 
 <ul>
   <li>Running analysis or reporting tools whose output does not need to be 100%
@@ -456,7 +456,7 @@ where FSX might be a vaiable option:</p>
      principles of operation are set in stone.</p>
 </div>
 
-</div>  <!-- fsx-usage-scennarios -->
+</div>  <!-- fsx-usage-scenarios -->
 
 <div class="h4" id="fsx-incompatibility">
 <h4>Incompatibility
@@ -473,9 +473,9 @@ FSX repository from one release to anoth
 
 <p>Dump and load is also the only upgrade path between FSFS and FSX.</p>
 
-<p>Finall, there is no guarantee that FSX will eventually be released at all.
+<p>Finally, there is no guarantee that FSX will eventually be released at all.
 That means even if you find it useful in your specific environment, we might
-decide to remvove FSX entirely from future releases.</p>
+decide to remove FSX entirely from future releases.</p>
 
 </div>  <!-- fsx-incompatibility -->
 



Mime
View raw message