Fixes after review

Author: wouterj

_build/spelling_word_list.txt

@@ -203,7 +203,7 @@ namespacing
 natively
 nd
 netmasks
-NGINX
+nginx
 normalizer
 normalizers
 npm

bundles/best_practices.rst

@@ -188,7 +188,7 @@ The index file (for example ``Resources/doc/index.rst`` or
 ``Resources/doc/index.md``) is the only mandatory file and must be the entry
 point for the documentation. The
 :doc:`reStructuredText (rST) </contributing/documentation/format>` is the format
-used to render the documentation on ``symfony.com``.
+used to render the documentation on the Symfony website.
 
 Installation Instructions
 ~~~~~~~~~~~~~~~~~~~~~~~~~

components/dotenv.rst

@@ -28,7 +28,7 @@ Sensitive information and environment-dependent settings should be defined as
 environment variables (as recommended for `twelve-factor applications`_). Using
 a ``.env`` file to store those environment variables eases development and CI
 management by keeping them in one "standard" place and agnostic of the
-technology stack you are using (NGINX vs PHP built-in server for instance).
+technology stack you are using (nginx vs PHP built-in server for instance).
 
 .. note::
 

components/http_foundation.rst

@@ -477,10 +477,10 @@ represented by a PHP callable instead of a string::
 
     Additionally, PHP isn't the only layer that can buffer output. Your web
     server might also buffer based on its configuration. Some servers, such as
-    NGINX, let you disable buffering at the config level or by adding a special HTTP
+    nginx, let you disable buffering at the config level or by adding a special HTTP
     header in the response::
 
-        // disables FastCGI buffering in NGINX only for this response
+        // disables FastCGI buffering in nginx only for this response
         $response->headers->set('X-Accel-Buffering', 'no')
 
 .. _component-http-foundation-serving-files:
@@ -517,7 +517,7 @@ Alternatively, if you are serving a static file, you can use a
 
 The ``BinaryFileResponse`` will automatically handle ``Range`` and
 ``If-Range`` headers from the request. It also supports ``X-Sendfile``
-(see for `NGINX`_ and `Apache`_). To make use of it, you need to determine
+(see for `nginx`_ and `Apache`_). To make use of it, you need to determine
 whether or not the ``X-Sendfile-Type`` header should be trusted and call
 :method:`Symfony\\Component\\HttpFoundation\\BinaryFileResponse::trustXSendfileTypeHeader`
 if it should::
@@ -665,7 +665,7 @@ Learn More
     /session/*
     /http_cache/*
 
-.. _NGINX: https://www.nginx.com/resources/wiki/start/topics/examples/xsendfile/
+.. _nginx: https://www.nginx.com/resources/wiki/start/topics/examples/xsendfile/
 .. _Apache: https://tn123.org/mod_xsendfile/
 .. _`JSON Hijacking`: http://haacked.com/archive/2009/06/25/json-hijacking.aspx
 .. _OWASP guidelines: https://www.owasp.org/index.php/OWASP_AJAX_Security_Guidelines#Always_return_JSON_with_an_Object_on_the_outside

configuration/external_parameters.rst

@@ -96,7 +96,7 @@ will be used whenever the corresponding environment variable is *not* found:
         $container->setParameter('env(DATABASE_HOST)', 'localhost');
 
 Setting environment variables is generally done at the web server level or in the
-terminal. If you're using Apache, NGINX or just the console, you can use e.g. one
+terminal. If you're using Apache, nginx or just the console, you can use e.g. one
 of the following:
 
 .. configuration-block::

create_framework/front_controller.rst

@@ -117,7 +117,7 @@ To access a page, you must now use the ``front.php`` script:
 
 .. tip::
 
-    Most web servers like Apache or NGINX are able to rewrite the incoming URLs
+    Most web servers like Apache or nginx are able to rewrite the incoming URLs
     and remove the front controller script so that your users will be able to
     type ``http://127.0.0.1:4321/hello?name=Fabien``, which looks much better.
 

deployment/heroku.rst

@@ -98,7 +98,7 @@ directory of the application and add just the following content:
 
 .. note::
 
-    If you prefer to use NGINX, which is also available on Heroku, you can create
+    If you prefer to use nginx, which is also available on Heroku, you can create
     a configuration file for it and point to it from your Procfile as described
     in the `Heroku documentation`_:
 

reference/forms/types/textarea.rst

@@ -30,7 +30,7 @@ Renders a ``textarea`` HTML element.
 .. tip::
 
     If you prefer to use an **advanced WYSIWYG editor** instead of a plain
-    text area, consider using the FOSCKEditorBundle community bundle. Read
+    ``<textarea>``, consider using the FOSCKEditorBundle community bundle. Read
     `its documentation`_ to learn how to integrate it in your Symfony application.
 
 Inherited Options

setup.rst

@@ -161,7 +161,7 @@ Running the Symfony Application
 -------------------------------
 
 On production servers, Symfony applications use web servers such as Apache or
-NGINX (see :doc:`configuring a web server to run Symfony </setup/web_server_configuration>`).
+nginx (see :doc:`configuring a web server to run Symfony </setup/web_server_configuration>`).
 However, on your local development machine you can also use the web server
 provided by Symfony, which in turn uses the built-in web server provided by PHP.
 
@@ -191,7 +191,7 @@ pressing ``Ctrl+C`` from the terminal or command console.
 .. tip::
 
     Symfony's web server is great for developing, but should **not** be
-    used on production. Instead, use Apache or NGINX.
+    used on production. Instead, use Apache or nginx.
     See :doc:`/setup/web_server_configuration`.
 
 Checking Symfony Application Configuration and Setup

setup/homestead.rst

@@ -52,7 +52,7 @@ configuration:
           to: /home/vagrant/projects/symfony_demo/web
           type: symfony
 
-The ``type`` option tells Homestead to use the Symfony NGINX configuration.
+The ``type`` option tells Homestead to use the Symfony nginx configuration.
 
 At last, edit the hosts file on your local machine to map ``symfony-demo.test``
 to ``192.168.10.10`` (which is the IP used by Homestead)::

setup/symfony_server.rst

@@ -1,7 +1,7 @@
 Symfony Local Web Server
 ========================
 
-You can run Symfony applications with any web server (Apache, NGINX, the
+You can run Symfony applications with any web server (Apache, nginx, the
 internal PHP web server, etc.). However, Symfony provides its own web server to
 make you more productive while developing your applications.
 

setup/web_server_configuration.rst

@@ -9,12 +9,12 @@ The preferred way to develop your Symfony application is to use
 
 However, when running the application in the production environment, you'll need
 to use a fully-featured web server. This article describes several ways to use
-Symfony with Apache or NGINX.
+Symfony with Apache or nginx.
 
 When using Apache, you can configure PHP as an
 :ref:`Apache module <web-server-apache-mod-php>` or with FastCGI using
 :ref:`PHP FPM <web-server-apache-fpm>`. FastCGI also is the preferred way
-to use PHP :ref:`with NGINX <web-server-nginx>`.
+to use PHP :ref:`with nginx <web-server-nginx>`.
 
 .. sidebar:: The Web Directory
 
@@ -251,10 +251,10 @@ instead:
 
 .. _web-server-nginx:
 
-NGINX
+nginx
 -----
 
-The **minimum configuration** to get your application running under NGINX is:
+The **minimum configuration** to get your application running under nginx is:
 
 .. code-block:: nginx
 
@@ -337,10 +337,10 @@ The **minimum configuration** to get your application running under NGINX is:
     By default, Symfony applications include several ``.htaccess`` files to
     configure redirections and to prevent unauthorized access to some sensitive
     directories. Those files are only useful when using Apache, so you can
-    safely remove them when using NGINX.
+    safely remove them when using nginx.
 
-For advanced NGINX configuration options, read the official `NGINX documentation`_.
+For advanced nginx configuration options, read the official `nginx documentation`_.
 
 .. _`Apache documentation`: https://httpd.apache.org/docs/
 .. _`FastCgiExternalServer`: https://docs.oracle.com/cd/B31017_01/web.1013/q20204/mod_fastcgi.html#FastCgiExternalServer
-.. _`NGINX documentation`: https://www.nginx.com/resources/wiki/start/topics/recipes/symfony/
+.. _`nginx documentation`: https://www.nginx.com/resources/wiki/start/topics/recipes/symfony/

web_link.rst

@@ -18,7 +18,7 @@ with HTTP 1.x:
 
 Something important to consider is that all these HTTP/2 features require a
 secure HTTPS connection, even when working on your local machine. The main web
-servers (Apache, NGINX, Caddy, etc.) support this, but you can also use the
+servers (Apache, nginx, Caddy, etc.) support this, but you can also use the
 `Docker installer and runtime for Symfony`_ created by Kévin Dunglas, from the
 Symfony community.