cosmetic changes in doc

Doc/Manual/Scilab.html

@@ -157,7 +157,7 @@ it may be because the SWIG library is not found. Check the <tt>SWIG_LIB</tt> env
 </p>
 
 <p>
-Note: SWIG for Scilab can work in two modes related to the way the module is build, see the <a href="#Scilab_building_modes">Building modes</a> section for details.
+Note: SWIG for Scilab can work in two modes related to the way the module is built, see the <a href="#Scilab_building_modes">Building modes</a> section for details.
 This example uses the <tt>builder</tt> mode.
 </p>
 
@@ -170,7 +170,7 @@ The <tt>swig</tt> executable has several other command line options you can use.
 <H3><a name="Scilab_running_swig_building_module"></a>37.2.2 Building the module</H3>
 
 <p>
-To be loaded in Scilab, the wrapper has to be build into a dynamic module (or shared library).
+To be loaded in Scilab, the wrapper has to be built into a dynamic module (or shared library).
 </p>
 
 <p>
@@ -183,7 +183,7 @@ $ gcc -shared example_wrap.o -o libexample.so
 </pre></div>
 
 <p>
-Note: we supposed in this example the path to the Scilab include directory is <tt>/usr/local/include/scilab</tt> (which is the case in a Debian environment), this sould be changed for another environment.
+Note: we supposed in this example that the path to the Scilab include directory is <tt>/usr/local/include/scilab</tt> (which is the case in a Debian environment), this should be changed for another environment.
 </p>
 
 <H3><a name="Scilab_running_swig_loading_module"></a>37.2.3 Loading the module</H3>
@@ -206,7 +206,7 @@ Link done.
 </pre></div>
 
 <p>
-Which means that Scilab has sucessfully loaded the shared library. The module functions and other symbols are now available in Scilab.
+which means that Scilab has successfully loaded the shared library. The module functions and other symbols are now available in Scilab.
 </p>
 
 <H3><a name="Scilab_running_swig_using_module"></a>37.2.4 Using the module</H3>
@@ -217,23 +217,29 @@ In Scilab, the function <tt>fact()</tt> is simply called as following:
 
 <div class="targetlang"><pre>
 --&gt; fact(5)
-ans =  120
+ans  =
+
+    120.
 </pre></div>
 
 <p>For the <tt>Foo</tt> global variable, the accessors need to be used:
 
 <div class="targetlang"><pre>
 --&gt; Foo_get
-ans =  3
+ans  =
+
+    3.
 
 --&gt; Foo_set(4);
 
 --&gt; Foo_get
-ans =  4
+ans  =
+
+    4.
 </pre></div>
 
 <p>
-Note: in order to be concise, the remaining Scilab code examples assume the modules have been successfully built and loaded in Scilab.
+Note: for conciseness, we assume in the subsequent Scilab code examples that the modules have been beforehand built and loaded in Scilab.
 </p>
 
 <H3><a name="Scilab_running_swig_options"></a>37.2.5 Scilab command line options</H3>
@@ -455,10 +461,14 @@ These functions are used as following:
 --&gt; Foo_set(4);
 
 --&gt; c
-c =  3
+c =
+
+    3.
 
 --&gt; Foo_get()
-ans =  4
+ans  =
+
+    4.
 </pre></div>
 
 <p>
@@ -498,8 +508,6 @@ It works the same:</p>
 
 --&gt; y_set([0:6] / 10);
 --&gt; y_get()
-
---&gt;
  ans  =
 
     0.    0.1    0.2    0.3    0.4    0.5    0.6
@@ -532,30 +540,45 @@ the following getter functions are generated:
 --&gt; exec loader.sce;
 --&gt; ICONST_get();
  ans  =
-      42
+
+    42.
+
 --&gt; FCONST_get();
  ans  =
+
     2.1828
+
 --&gt; CCONST_get();
  ans  =
+
     x
+
 --&gt; CCONST2_get();
  ans  =
 
 --&gt; SCONST_get();
  ans  =
+
     Hello World
+
 --&gt; SCONST2_get();
  ans  =
+
     "Hello World"
+
 --&gt; EXPR_get();
  ans  =
+
     48.5484
+
 --&gt; iconst_get();
  ans  =
-       37
+
+    37.
+
 --&gt; fconst_get();
  ans  =
+
     3.14
 </pre></div>
 
@@ -591,30 +614,45 @@ are mapped to Scilab variables, with the same name:
 --&gt; exec loader.sce;
 --&gt; ICONST
  ans  =
+
     42
+
 --&gt; FCONST
  ans  =
+
     2.1828
+
 --&gt; CCONST
  ans  =
+
     x
+
 --&gt; CCONST2
  ans  =
 
 --&gt; SCONST
  ans  =
+
     Hello World
+
 --&gt; SCONST2
  ans  =
+
     "Hello World"
+
 --&gt; EXPR
  ans  =
+
     48.5484
+
 --&gt; iconst
  ans  =
+
     37
+
 --&gt; fconst
  ans  =
+
     3.14
 </pre></div>
 
@@ -638,12 +676,17 @@ a getter function will be generated for each value of the enumeration:
 --&gt; exec loader.sce;
 --&gt; RED_get()
  ans  =
+
     0.
+
 --&gt; BLUE_get()
  ans  =
+
     1.
+
 --&gt; GREEN_get()
  ans  =
+
     2.
 </pre></div>
 
@@ -661,13 +704,19 @@ typedef enum { RED, BLUE, GREEN } color;
 --&gt; exec loader.sce;
 --&gt; RED
  ans  =
+
     0.
+
 --&gt; BLUE
  ans  =
+
     1.
+
 --&gt; GREEN
  ans  =
+
     2.
+
 </pre></div>
 </p>
 
@@ -894,6 +943,7 @@ can be used in Scilab like this:
 --&gt; p2 = Point_new(1, 2);
 --&gt; p1.distance(p2)
 ans  =
+
     3.6056
 
 --&gt; delete_Point(p1);
@@ -1344,7 +1394,7 @@ The following table provides the equivalent Scilab type for C/C++ primitive type
 <p>
 Notes:
 <ul>
-<li>In Scilab the <tt>double</tt> type is used far more than any integer type.
+<li>In Scilab the <tt>double</tt> type is far more used than any integer type.
 This is why integer values (<tt>int32</tt>, <tt>uint32</tt>, ...) are automatically converted to Scilab <tt>double</tt> values when marshalled from C into Scilab.
 Additionally on input to a C function, Scilab <tt>double</tt> values are converted into the related integer type.
 </li>