Fix some issues with previous cs docs

Author: cconard96

source/coding_standards/javascript.rst

@@ -13,7 +13,7 @@ Starting with GLPI 9.5.0, the target version was bumped to 6 (2015).
 Functions
 ---------
 
-Function names must be written in *camelCaps*:
+Function names must be written in *camelCase*:
 
 .. code-block:: JavaScript
 
@@ -37,7 +37,7 @@ Classes
 
 If you are writing code for versions of GLPI before 9.5.0, you may not use classes as class support was added in EMCAScript 6.
 
-Class names must be written in `PascalCase`.
+Class names must be written in *PascalCase*.
 
 ..code-block:: JavaScript
 

source/coding_standards/php.rst

@@ -9,7 +9,7 @@ Arrays must be declared using the short notation syntax (``[]``), long notation
 Including files
 ---------------
 
-Use ``include_once`` in order to include the file once and to raise warning if file does not exists:
+Use ``include_once`` in order to include the file once and to raise warning if file does not exist:
 
 .. code-block:: php
 
@@ -31,7 +31,7 @@ The PHP closing tag ``?>`` must be avoided on full PHP files (so in most of GLPI
 Functions
 ---------
 
-Function names must be written in *camelCaps*:
+Function names must be written in *camelCase*:
 
 .. code-block:: php
 
@@ -40,9 +40,9 @@ Function names must be written in *camelCaps*:
       //do something here!
    }
 
-Space after opening parenthesis and before closing parenthesis are forbidden. For parematers which have a default value; add a space before and after the equel sign.
+Space after opening parenthesis and before closing parenthesis are forbidden. For parameters which have a default value, add a space before and after the equals sign.
 
-If parameters add block doc for these parameters, please see the `Comments`_ section for any example.
+If the function has parameters, add doc block for these parameters. Please see the `Comments`_ section for an example.
 
 If function from parent add
 
@@ -51,7 +51,7 @@ If function from parent add
    <?php
    function getMenuContent()
 
-If it's a new function, add in block doc (see the `Comments`_ section):
+If it's a new function, add the `@since` tag in the doc block (see the `Comments`_ section):
 
 .. code-block:: php
 
@@ -96,9 +96,9 @@ On the other hand; if you already have an object instance; you should better use
 Classes
 -------
 
-Class names must be written in `CamelCase`:
+Class names must be written in *PascalCase*:
 
-GLPI do not use `PHP namespaces <http://php.net/manual/en/language.namespaces.php>`_ right now; so be careful when creating new classes to take a name that does not exists yet.
+Most of the GLPI code does not use or support `PHP namespaces <http://php.net/manual/en/language.namespaces.php>`_ yet. Therefore, you will need to be careful when creating new classes to take a name that does not exists yet.
 
 .. code-block:: php
 
@@ -108,9 +108,9 @@ GLPI do not use `PHP namespaces <http://php.net/manual/en/language.namespaces.ph
    }
 
 
-Note: even if GLPI does not use namespaces, some libs does, you will have to take care of that. You can also if you wish use namespaces for PHP objects call.
+Note: You can use namespaces for PHP classes if you want, but you should be aware that there are some parts of the code that still don't support them. As a good rule, avoid using a namespaced class to extend CommonDBTM.
 
-For example, the folloging code:
+For example, the following code:
 
 .. code-block:: php
 
@@ -137,6 +137,8 @@ Could also be written as (see the ``\``):
       ...
    }
 
+When referring to classes in another namespace you SHOULD use `use` statements instead of using the full name.
+
 Comments
 --------
 
@@ -170,9 +172,9 @@ For each method or function documentation, you'll need at least to have a descri
       //[...]
    }
 
-Some other informations way be added; if the function requires it.
+Some other information may be added if the function requires it.
 
-Refer to the `PHPDocumentor website <https://phpdoc.org/docs/latest>`_ to get more informations on documentation. The `latest GLPI API documentation <https://forge.glpi-project.org/projects/glpi/embedded/index.html>`_ is also available online.
+Refer to the `PHPDocumentor website <https://phpdoc.org/docs/latest>`_ to get more information on documentation. The `latest GLPI API documentation <https://forge.glpi-project.org/projects/glpi/embedded/index.html>`_ is also available online.
 
 Please follow the order defined below:
 
@@ -193,7 +195,7 @@ Parameters documentation
 Each parameter must be documented in its own line, begining with the ``@param`` tag, followed by the `Variables types`_, followed by the param name (``$param``), and finally with the description itself.
 If your parameter can be of different types, you can list them separated with a ``|`` or you can use the ``mixed`` type; it's up to you!
 
-All parameters names and description must be aligned vertically on the longest (plu one character); see the above example.
+All parameters names and description must be aligned vertically on the longest (plus one character); see the above example.
 
 Override method: @inheritDoc? @see? docblock? no docblock?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^