[pull] main from django:main

docs/internals/contributing/new-contributors.txt

@@ -52,10 +52,11 @@ expected. Updating a patch is both useful and important! See more on
 Write some documentation
 ------------------------
 
-Django's documentation is great but it can always be improved. Did you find a
-typo? Do you think that something should be clarified? Go ahead and suggest a
-documentation patch! See also the guide on
-:doc:`/internals/contributing/writing-documentation`.
+Django's documentation is extensive, but it can always be improved. Changes
+that materially improve its correctness, clarity, or completeness are welcome.
+A minor rewording or pure typo fix is generally not suitable as a standalone
+contribution, but may be included as part of a more substantial patch. See
+also the guide on :doc:`/internals/contributing/writing-documentation`.
 
 .. note::
 

docs/internals/contributing/writing-code/submitting-patches.txt

@@ -11,9 +11,12 @@ without a solution.
 Typo fixes and trivial documentation changes
 ============================================
 
-If you are fixing a really trivial issue, for example changing a word in the
-documentation, the preferred way to provide the patch is using GitHub pull
-requests without a Trac ticket.
+If you've contributed to Django before and just want to fix a really trivial
+issue, for example changing a word in the documentation, the preferred way to
+provide the patch is using GitHub pull requests without a Trac ticket. If you
+haven't contributed before, a minor rewording or pure typo fix is generally not
+suitable as a first contribution, but may be included as part of a more
+substantial patch for an accepted ticket.
 
 See :doc:`/internals/contributing/writing-code/working-with-git` for more
 details on how to use pull requests.