Update mentioning of pgsphere in the docs

Author: kimakan

README.md

@@ -63,9 +63,9 @@ to install the generated parser in your virtual environment.
 Additional requirements
 -----------------------
 The queryparser assumes that the PostgreSQL database has the extension
-[pg_sphere](https://github.com/kimakan/pgsphere/tree/aiprdbms16) installed.
-Although the `pg_sphere` is not required for the python module, the PostgreSQL
-**queries will not run** without this extension installed on the database.
+[pg_sphere](https://github.com/postgrespro/pgsphere) installed.
+Although `pg_sphere` is not required for the Python module, PostgreSQL
+**queries will not run** without this extension installed in the database.
 
 
 Parsing MySQL and PostgreSQL
@@ -120,7 +120,7 @@ the `ADQLQueryTranslator` class
 
 ```python
 from queryparser.adql import ADQLQueryTranslator
-adql = "SELECT TOP 100 POINT('ICRS', ra, de) FROM db.tab;"
+adql = "SELECT TOP 100 POINT('ICRS', ra, dec) FROM db.tab;"
 adt = ADQLQueryTranslator(adql)
 ```
 
@@ -130,7 +130,7 @@ and calling
 adt.to_postgresql()
 ```
 
-which returns a translated string representing a valid MySQL query if
+which returns a translated string representing a valid PostgreSQL query if
 the ADQL query had no errors. The PostgreSQL query can then be parsed with the
 `PostgreSQLQueryProcessor` in the same way as shown above.
 
@@ -149,4 +149,3 @@ then run the test suite with
 ```bash
 python -m pytest lib/
 ```
-

docs/development.md

@@ -9,8 +9,7 @@ processed and can be used to check, for example, for permissions before the
 query is sent to the server.
 
 In addition, queryparser can also work with ADQL queries which can be translated
-to either MySQL or PostgreSQL language and then further processed the same
-way.
+to PostgreSQL and then further processed the same way.
 
 Below is a more detailed description along with instructions for anyone who is
 interested in further developing the package.
@@ -49,14 +48,14 @@ Individual dialect functionality (MySQL in this case) with increased verbosity
 can be tested with
 
 ```bash
-pytest /lib/queryparser/testing/test_mysql.py -v
+pytest lib/queryparser/testing/test_mysql.py -v
 ```
 
 Individual tests (20th MySQL test in this case, but otherwise any test
 that includes the string 't20') are ran with
 
 ```bash
-pytest /lib/queryparser/testing/test_mysql.py -k t20
+pytest lib/queryparser/testing/test_mysql.py -k t20
 ```
 
 If the package `pytest-cov` is installed then the detailed coverage report
@@ -120,7 +119,7 @@ and an ADQL translator. The processors accept any SELECT-like query and
 after the process_query() method has been executed, several elements of
 the query are extracted (all touch columns and tables, used keywords and functions).
 Before the processing the query is validated and invalid queries are rejected.
-The ADQL translator allows translating valid ADQL queries to MySQL or PostgreSQL.
+The ADQL translator allows translating valid ADQL queries to PostgreSQL.
 
 Most of the processor code is shared between MySQL and PostgreSQL and is
 therefore merged together inside of the `common.py`. This file consists