Additional fix to markdown format.

Author: darold

README.md

@@ -1,5 +1,5 @@
 External file access extension
-------------------------------
+==============================
 
 Allow access to "external files" from PostgreSQL server file systems.
 This extension is only a "secure version" of the server side lo_* functions.
@@ -10,15 +10,15 @@ A BFILE column stores a file locator that points to an external file containing
 the data: (DIRECTORY, FILENAME). Here the data type is called EFILE.
 
 
-1. Installation requirements
-----------------------------
+Installation requirements
+-------------------------
 
 
 PostgreSQL 9.1 or better are required.
 User with PostgreSQL superuser role for creating extension.
 
-2. Installation
----------------
+Installation
+------------
 
 external_file has been written as a PostgreSQL extension and uses the Extension
 Building Infrastructure "PGXS".
@@ -55,8 +55,8 @@ change the default search path at user level too.
 Please refer to the PostgreSQL documentation for more information.
 
 
-3. Usage
---------
+Usage
+-----
 
 External file are accessed using two values, an alias for the path of the
 directory where the file is, and the file name.
@@ -115,8 +115,8 @@ Example:
 	(2 lines)
 
 
-4. Function reference
----------------------
+Function reference
+------------------
 
 * **readEfile(e_file in efile) returns bytea**
 
@@ -139,18 +139,18 @@ Example:
   full path for the file, otherwise an error is generated 
   useful to check if session user has access to this external file
 
-5. License
-----------
+License
+-------
 
 Author Dominique Legendre
 
-Copyright (c) 2012-2015 Brgm - All rights reserved.
+Copyright (c) 2012-2018 Brgm - All rights reserved.
 
 See LICENCE file.
 
 
-6. Acknowledgements
--------------------
+Acknowledgements
+----------------
 
 Great thanks to Gilles Darold for code review, security patches and project hosting.