Fix Intersphinx mapping errors with Flask + minor RST bugs

Author: EtiennePelletier

doc/errors.rst

@@ -141,8 +141,8 @@ that you can do with Flask/Blueprint :meth:`@errorhandler <flask:flask.Flask.err
     @api.errorhandler(RootException)
     def handle_root_exception(error):
         '''Return a custom message and 400 status code'''
-        return {'message': 'What you want'}, 400       
-        
+        return {'message': 'What you want'}, 400
+
 
     @api.errorhandler(CustomException)
     def handle_custom_exception(error):
@@ -160,14 +160,14 @@ that you can do with Flask/Blueprint :meth:`@errorhandler <flask:flask.Flask.err
     def handle_fake_exception_with_header(error):
         '''Return a custom message and 400 status code'''
         return {'message': error.message}, 400, {'My-Header': 'Value'}
-        
-        
+
+
     @api.errorhandler(NoResultFound)
     def handle_no_result_exception(error):
         '''Return a custom not found error message and 404 status code'''
-        return {'message': error.specific}, 404        
-        
-        
+        return {'message': error.specific}, 404
+
+
 .. note ::
 
     A "NoResultFound" error with description is required by the OpenAPI 2.0 spec. The docstring in the error handle function is output in the swagger.json as the description.

doc/quickstart.rst

@@ -23,13 +23,15 @@ All you need to do is update your requirements to use Flask-RESTX instead of
 Flask-RESTPlus. Then you need to update all your imports.
 This can be done using something like:
 
-::
+.. code-block:: bash
+
    find . -type f -name "*.py" | xargs sed -i "s/flask_restplus/flask_restx/g"
 
 Finally, you will need to update your configuration options (described `here
-<quickstart.html#configuration>`_). Example:
+<configuration.html>`_). Example:
+
+.. code-block:: bash
 
-::
    find . -type f -name "*.py" | xargs sed -i "s/RESTPLUS_/RESTX_/g"
 
 
@@ -112,7 +114,7 @@ See :ref:`swaggerui` for a complete documentation on the automatic documentation
 Resourceful Routing
 -------------------
 The main building block provided by Flask-RESTX are resources.
-Resources are built on top of :ref:`Flask pluggable views <flask:views>`,
+Resources are built on top of :doc:`Flask pluggable views <flask:views>`,
 giving you easy access to multiple HTTP methods just by defining methods on your resource.
 A basic CRUD resource for a todo application (of course) looks like this:
 

doc/scaling.rst

@@ -38,7 +38,7 @@ Here's an example directory structure::
 
 
 The `app` module will serve as a main application entry point following one of the classic
-Flask patterns (See :ref:`flask:larger-applications` and :ref:`flask:app-factories`).
+Flask patterns (See :doc:`flask:patterns/packages` and :doc:`flask:patterns/appfactories`).
 
 The `core` module is an example, it contains the business logic.
 In fact, you call it whatever you want, and there can be many packages.
@@ -151,7 +151,7 @@ Using this pattern, you simply have to register your API in `app.py` like that:
 Use With Blueprints
 -------------------
 
-See :ref:`blueprints` in the Flask documentation for what blueprints are and why you should use them.
+See :doc:`flask:blueprints` in the Flask documentation for what blueprints are and why you should use them.
 Here's an example of how to link an :class:`Api` up to a :class:`~flask.Blueprint`.
 
 .. code-block:: python