text improvement request for deployment guide

[JorisBenschop]

The current text on deployment (​https://docs.djangoproject.com/en/dev/howto/deployment/) says:

Django’s chock-full of shortcuts to make Web developer’s lives easier, but all those tools are of
no use if you can’t easily deploy your sites. Since Django’s inception, ease of deployment
has been a major goal. There’s a number of good ways to easily deploy Django:
How to deploy with WSGI
Deployment checklist

Its a bit strange to state "a number of good ways", and then present the reader with exactly one method. Ideally I'd like to see a suggestion to host multiple sites one one server without weird tricks, but at least it may be good to indicate there is ony a single method recommended to deploy when there is indeed only one method... so maybee like this:

Django’s chock-full of shortcuts to make Web developer’s lives easier, but all those tools are of
no use if you can’t easily deploy your sites. Since Django’s inception, ease of deployment
has been a major goal. THe best way to deploy Django is through WSGI:
How to deploy with WSGI
Deployment checklist

[Tim Graham]

Yes, FastCGI was deprecated and now removed in master so the text you propose is okay though we can probably just chop "There’s a number of good ways to easily deploy Django:" without replacement. While we're there, it might be best to remove the outdated reference to Django Book or update the note to mention that it's discussion of FastCGI is also outdated.

[Yamila]

PR: ​https://github.com/django/django/pull/4791

[Markus Holtermann <info@…>]

In f954c51:

Fixed #24926 -- Removed outdated information from deployment