diff --git a/docs/ref/contrib/auth.txt b/docs/ref/contrib/auth.txt
index 6395949e3e..402496a2db 100644
--- a/docs/ref/contrib/auth.txt
+++ b/docs/ref/contrib/auth.txt
@@ -571,7 +571,7 @@ The following backends are available in :mod:`django.contrib.auth.backends`:
         permission string ``perm``. Returns ``False`` if the user is not
         :attr:`~django.contrib.auth.models.CustomUser.is_active`.
 
-    .. method:: has_module_perms(self, user_obj, app_label)
+    .. method:: has_module_perms(user_obj, app_label)
 
         Returns whether the ``user_obj`` has any permissions on the app
         ``app_label``.
diff --git a/docs/ref/forms/widgets.txt b/docs/ref/forms/widgets.txt
index b5d4fc3d5d..c17877545b 100644
--- a/docs/ref/forms/widgets.txt
+++ b/docs/ref/forms/widgets.txt
@@ -263,7 +263,7 @@ foundation for custom widgets.
         ``Widget`` subclasses can provide custom context values by overriding
         this method.
 
-    .. method:: id_for_label(self, id_)
+    .. method:: id_for_label(id_)
 
         Returns the HTML ID attribute of this widget for use by a ``<label>``,
         given the ID of the field. Returns ``None`` if an ID isn't available.
diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt
index f6f224fbdf..731a280939 100644
--- a/docs/ref/models/expressions.txt
+++ b/docs/ref/models/expressions.txt
@@ -720,7 +720,7 @@ calling the appropriate methods on the wrapped expression.
               clone.expression = self.expression.relabeled_clone(change_map)
               return clone
 
-    .. method:: convert_value(self, value, expression, connection, context)
+    .. method:: convert_value(value, expression, connection, context)
 
         A hook allowing the expression to coerce ``value`` into a more
         appropriate type.
diff --git a/docs/ref/models/lookups.txt b/docs/ref/models/lookups.txt
index efa38d9a41..bd9831e23d 100644
--- a/docs/ref/models/lookups.txt
+++ b/docs/ref/models/lookups.txt
@@ -79,7 +79,7 @@ field references, aggregates, and ``Transform`` are examples that follow this
 API. A class is said to follow the query expression API when it implements the
 following methods:
 
-.. method:: as_sql(self, compiler, connection)
+.. method:: as_sql(compiler, connection)
 
     Responsible for producing the query string and parameters for the expression.
     The ``compiler`` is an ``SQLCompiler`` object, which has a ``compile()``
@@ -95,7 +95,7 @@ following methods:
     override the generation of the SQL string. See :meth:`Func.as_sql` for
     example usage.
 
-.. method:: as_vendorname(self, compiler, connection)
+.. method:: as_vendorname(compiler, connection)
 
     Works like ``as_sql()`` method. When an expression is compiled by
     ``compiler.compile()``, Django will first try to call ``as_vendorname()``,
diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt
index 2057c370f3..25563c19b7 100644
--- a/docs/ref/templates/api.txt
+++ b/docs/ref/templates/api.txt
@@ -167,7 +167,7 @@ what's passed by :class:`~django.template.backends.django.DjangoTemplates`.
     Loads a template with the given name, compiles it and returns a
     :class:`Template` object.
 
-.. method:: Engine.select_template(self, template_name_list)
+.. method:: Engine.select_template(template_name_list)
 
     Like :meth:`~Engine.get_template`, except it takes a list of names
     and returns the first template that was found.