Fixed #30573 -- Rephrased documentation to avoid words that minimise the involved difficulty.

This patch does not remove all occurrences of the words in question.
Rather, I went through all of the occurrences of the words listed
below, and judged if they a) suggested the reader had some kind of
knowledge/experience, and b) if they added anything of value (including
tone of voice, etc). I left most of the words alone. I looked at the
following words:

- simply/simple
- easy/easier/easiest
- obvious
- just
- merely
- straightforward
- ridiculous

Thanks to Carlton Gibson for guidance on how to approach this issue, and
to Tim Bell for providing the idea. But the enormous lion's share of
thanks go to Adam Johnson for his patient and helpful review.

docs/topics/settings.txt

@@ -104,9 +104,8 @@ that's redundant.
 Seeing which settings you've changed
 ------------------------------------
 
-There's an easy way to view which of your settings deviate from the default
-settings. The command ``python manage.py diffsettings`` displays differences
-between the current settings file and Django's default settings.
+The command ``python manage.py diffsettings`` displays differences between the
+current settings file and Django's default settings.
 
 For more, see the :djadmin:`diffsettings` documentation.
 
@@ -161,7 +160,7 @@ Creating your own settings
 ==========================
 
 There's nothing stopping you from creating your own settings, for your own
-Django apps. Just follow these guidelines:
+Django apps, but follow these guidelines:
 
 * Setting names must be all uppercase.
 * Don't reinvent an already-existing setting.
@@ -248,7 +247,7 @@ is accessed.
 
 If you set ``DJANGO_SETTINGS_MODULE``, access settings values somehow, *then*
 call ``configure()``, Django will raise a ``RuntimeError`` indicating
-that settings have already been configured. There is a property just for this
+that settings have already been configured. There is a property for this
 purpose:
 
 .. attribute: django.conf.settings.configured