Fix docs generation

Author: avalentino

docs/bands_example.rst

@@ -4,7 +4,7 @@ Exporting band data
 .. index:: ENVISAT, band, raster
 
 This tutorial shows how to convert ENVISAT_ raster information from dataset
-and generate flat binary rasters using PyEPR_.
+and generate flat binary (raster) files using PyEPR_.
 
 The program generates as many raster as the dataset specified in input.
 

docs/gdal_export_example.rst

@@ -79,7 +79,7 @@ It is a description of a raster file that the GDAL_ library uses for low level
 data access.
 Of course the entire machinery works because data in :class:`epr.Band`\s and
 :class:`epr.Dataset`\ s of ENVISAT_ products are stored as contiguous
-rasters.
+raster files.
 
 .. raw:: latex
 

docs/index.rst

@@ -52,8 +52,6 @@ ENVISAT Product Reader Python API
     * `CI status page <https://github.com/avalentino/pyepr/actions>`_
     * `PyEPR project page on PyPi <http://pypi.python.org/pypi/pyepr>`_
     * EPR-API `project page <https://github.com/bcdev/epr-api>`_
-    * EPR-API `documentation
-      <https://rawgithub.com/bcdev/epr-api/master/docs/epr_c_api/index.html>`_
 
     __ PyEPR_
 
@@ -108,6 +106,6 @@ but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 You should have received a copy of the GNU General Public License
-along with PyEPR.  If not, see <http://www.gnu.org/licenses/>.
+along with PyEPR.  If not, see <https://www.gnu.org/licenses/>.
 
-.. _`GNU General Public License`: http://www.gnu.org/licenses/gpl-3.0.html
+.. _`GNU General Public License`: https://www.gnu.org/licenses/gpl-3.0.html

docs/interactive_use.rst

@@ -311,7 +311,7 @@ Dealing with image data is simple as well::
 .. figure:: images/ASA_IMP_crop.*
    :width: 100%
 
-   Image data read from the "proc_data" band
+   Image data read from the `proc_data`` band
 
 
 .. _iterable: https://docs.python.org/3/glossary.html#term-iterable

docs/spelling_wordlist.txt

@@ -2,6 +2,7 @@ api
 config
 constness
 Cythonizing
+de
 dev
 distutils
 docstrings
@@ -31,7 +32,9 @@ roduct
 scanline
 sdist
 src
+str
 toml
 uchar
 vapour
 unittests
+vectorized

docs/usermanual.rst

@@ -229,7 +229,7 @@ Python vs C API
 ---------------
 
 The Python_ EPR API is fully object oriented.
-The main structures of the `C API`_ have been implemented as objects while
+The main structures of the C API have been implemented as objects while
 C function have been logically grouped and mapped onto object methods.
 
 The entire process of defining an object oriented API for Python_ has
@@ -239,8 +239,6 @@ API,
 Of course there are also some differences that are illustrated in the
 following sections.
 
-.. _`C API`: https://rawgit.com/bcdev/epr-api/master/docs/epr_c_api/index.html
-
 
 .. index:: memory, product
    pair: allocation; de-allocation