svn commit: r881197 [2/2] - in /websites/staging/directory/trunk/content: ./ apacheds/ apacheds/advanced-ug/ apacheds/basic-ug/ apacheds/configuration/ mavibot/ mavibot/user-guide/ studio/

[bu...@apache.org]

Modified: websites/staging/directory/trunk/content/mavibot/user-guide/2.2-physical-storage.html
==============================================================================
--- websites/staging/directory/trunk/content/mavibot/user-guide/2.2-physical-storage.html (original)
+++ websites/staging/directory/trunk/content/mavibot/user-guide/2.2-physical-storage.html Fri Oct  4 17:51:33 2013
@@ -156,7 +156,7 @@ it's something we might want to change l
 </blockquote>
 <h2 id="general-file-structure">General file structure</h2>
 <p>The file we use to store the data is a plain binary file, used to store all the BTrees. We can store many btrees in one single file.</p>
-<p>This file is considered as a fileSystem, with fixed size 'pages' (a page is an array of bytes). The page size is arbitrary fixed when teh RecordManager is created, and we will store every logical data n those physical pages, which will require to spread the logical data in many pages in most of the cases.</p>
+<p>This file is considered as a fileSystem, with fixed size 'pages' (a page is an array of bytes). The page size is arbitrary fixed when the RecordManager is created, and we will store every logical data n those physical pages, which will require to spread the logical data in many pages in most of the cases.</p>
 <h3 id="pageio">PageIO</h3>
 <p>Let's first introduce the <em>PageIO</em>, which is used to store the data on disk.</p>
 <p>A <em>PageIO</em> contains some raw data. As we have to map some logical data that may be wider than a physical fixed size <em>PageIO</em>, we use potentially more than one <em>PageIO</em> to store the data, and we link the <em>PageIO</em>s alltogether.</p>

Modified: websites/staging/directory/trunk/content/special-thanks.html
==============================================================================
--- websites/staging/directory/trunk/content/special-thanks.html (original)
+++ websites/staging/directory/trunk/content/special-thanks.html Fri Oct  4 17:51:33 2013
@@ -150,7 +150,7 @@
 </ul>
 <p>Thanks !</p>
 <h2 id="organizations-who-helped-our-project">Organizations who helped our project ...</h2>
-<p>We would also like to thank the oganizations who provided some tools and images for free :</p>
+<p>We would also like to thank the organizations who provided some tools and images for free :</p>
 <table>
 <thead>
 <tr>

Modified: websites/staging/directory/trunk/content/studio/internationalization.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/internationalization.html (original)
+++ websites/staging/directory/trunk/content/studio/internationalization.html Fri Oct  4 17:51:33 2013
@@ -131,7 +131,7 @@
 
 
 <h1 id="internationalization-i18n">Internationalization (i18n)</h1>
-<p>It exists a good guide on internationalisation (and externalizing string) at <a href="http://www.eclipse.org/articles/Article-Internationalization/how2I18n.html">How to Internationalize your Eclipse Plug-In</a>.</p>
+<p>It exists a good guide on internationalization (and externalizing string) at <a href="http://www.eclipse.org/articles/Article-Internationalization/how2I18n.html">How to Internationalize your Eclipse Plug-In</a>.</p>
 <h2 id="translating-the-current-code">Translating the current code</h2>
 <p>Translating Studio is not an simple task. There are many files to translate :</p>
 <ul>
@@ -159,7 +159,7 @@
 </ul>
 <p>Hints:</p>
 <ul>
-<li>Using Eclipse' Property-Editor in the 'Properties' view will prevent you from comming into troubles with uncomment characters like e.g. the German 'Umlauts'</li>
+<li>Using Eclipse' Property-Editor in the 'Properties' view will prevent you from getting into troubles with uncomment characters like e.g. the German 'Umlauts'</li>
 </ul>