Refs #36485 -- Removed unnecessary parentheses in :meth: and :func: roles in docs.

docs/howto/custom-file-storage.txt

@@ -29,7 +29,7 @@ You'll need to follow these steps:
                     option = settings.CUSTOM_STORAGE_OPTIONS
                 ...
 
-#. Your storage class must implement the :meth:`_open()` and :meth:`_save()`
+#. Your storage class must implement the :meth:`_open` and :meth:`_save`
    methods, along with any other methods appropriate to your storage class. See
    below for more on these methods.
 

docs/howto/custom-template-tags.txt

@@ -509,7 +509,7 @@ Simple block tags
 
 When a section of rendered template needs to be passed into a custom tag,
 Django provides the ``simple_block_tag`` helper function to accomplish this.
-Similar to :meth:`~django.template.Library.simple_tag()`, this function accepts
+Similar to :meth:`~django.template.Library.simple_tag`, this function accepts
 a custom tag function, but with the additional ``content`` argument, which
 contains the rendered content as defined inside the tag. This allows dynamic
 template sections to be easily incorporated into custom tags.

docs/howto/writing-migrations.txt

@@ -37,7 +37,7 @@ attribute::
             migrations.RunPython(forwards),
         ]
 
-You can also provide hints that will be passed to the :meth:`allow_migrate()`
+You can also provide hints that will be passed to the :meth:`allow_migrate`
 method of database routers as ``**hints``:
 
 .. code-block:: python
@@ -197,7 +197,7 @@ a transaction by setting the ``atomic`` attribute to ``False``::
 
 Within such a migration, all operations are run without a transaction. It's
 possible to execute parts of the migration inside a transaction using
-:func:`~django.db.transaction.atomic()` or by passing ``atomic=True`` to
+:func:`~django.db.transaction.atomic` or by passing ``atomic=True`` to
 ``RunPython``.
 
 Here's an example of a non-atomic data migration that updates a large table in