Don't use ordered Meta, schemas are always ordered

docs/openapi.rst

@@ -242,23 +242,9 @@ schema `properties`. Although objects are not ordered in JSON, OpenAPI
 graphical interfaces tend to respect the order in which the `properties` are
 defined in the ``properties`` object in the specification file.
 
-When using an ordererd ``Schema``, the fields definition order is preserved
-when generating the specification file and the `properties` are displayed in
-that order.
+``Schema`` classes keep fields in declaration order, and this order is preserved when
+generating the specification file: the `properties` are displayed in that order.
 
-This is typically done in a base class:
-
-.. code-block:: python
-    :emphasize-lines: 2,3
-
-    class MyBaseSchema(ma.Schema):
-        class Meta:
-            ordered = True
-
-
-    class User(MyBaseSchema):
-        name = ma.fields.String()
-        surname = ma.fields.String()
 
 Serve the OpenAPI Documentation
 -------------------------------

src/flask_smorest/pagination.py

@@ -59,7 +59,6 @@ class PaginationParametersSchema(ma.Schema):
         """Deserializes pagination params into PaginationParameters"""
 
         class Meta:
-            ordered = True
             unknown = ma.EXCLUDE
 
         page = ma.fields.Integer(
@@ -127,9 +126,6 @@ class PaginationMetadataSchema(ma.Schema):
     previous_page = ma.fields.Int()
     next_page = ma.fields.Int()
 
-    class Meta:
-        ordered = True
-
 
 PAGINATION_HEADER = {
     "description": "Pagination metadata",

tests/conftest.py

@@ -69,7 +69,6 @@ class DocSchema(CounterSchema):
 
     class QueryArgsSchema(ma.Schema):
         class Meta:
-            ordered = True
             unknown = ma.EXCLUDE
 
         arg1 = ma.fields.String()