minor editorial changes

diff --git a/tests/selenium/README b/tests/selenium/README
index 43eb3befba1c1b458bbf5ab986573a411404d60a..9f797ce8ef9fc23e7b8fc5ebd2d9de2969f19524 100644 (file)
--- a/tests/selenium/README
+++ b/tests/selenium/README
@@ -1,32 +1,33 @@
 HowTo run the tests follow these steps :
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-1/ Create & configure your ./tests/selenium/config.test.php (See sample one in ./tests/selenium/config.inc.php-dist).
-2/ Run the ./build_tests.php script
-       This script build the TestSuite.html file and all the related html tests files in ./tests/selenium/static/.
+1. Create & configure your ./tests/selenium/config.test.php (See sample one in ./tests/selenium/config.inc.php-dist).
+2. Run the ./build_tests.php script
+       This script builds the TestSuite.html file and all the related html tests files in ./tests/selenium/static/.
        It builds one directory for each server selected to run the tests in your ./tests/selenium/config.inc.php
-       and create the static selenium html test files for each of them.
-3/ open your browser and go to http://$webUrl/
-       Where $webUrl is the value setted in your ./tests/selenium/config.inc.php
-4/ click on "Selenium tests" on the PPA intro page & run the tests using the "Selenium TestRunner" buttons in the top-right frame.
+       and creates the static selenium html test files for each of them.
+3. Open your browser and go to http://$webUrl/
+       Where $webUrl is the value set in your ./tests/selenium/config.inc.php
+4. Click on "Selenium tests" on the PPA intro page & run the tests using the "Selenium TestRunner" buttons in the top-right frame.
 
 Enjoy the tests.
 
-HowTo write new test:
+
+HowTo write new tests:
 ~~~~~~~~~~~~~~~~~~~~~
 The selenium's HTML tests files cannot behave differently in regard to the PG backend where the tests are run on. In order to address
 this issue we are using "test-builder" scripts to create these static HTML files. These scripts are connected to each backends using
 the PPA database classes and allow you to use their methods, and especialy the $data->has*() ones,  throught the $data variable like 
 in any other ppa script.
 
-1/ how build_tests is working and why
+1. how build_tests is working and why
 The build_tests.php script is processing the test-builders scripts from ./tests/selenium/src in alphanumeric order. That's why each
 test-builder's name should follow these rules: begin with 2numeric number, then -, then the script name (ex. 01-test1.php or 46-test46.php).
 
 It allows to enforce the order the scripts will be run during the testSuite. This way, column's tests could be run *after* the table's tests
 in the test suite and use the previous created tables.
 
-2/ how test-builder are working
+2. how test-builder are working
 
 These scripts are included and executed in the build_tests.php in alphanumeric order.
 They should: