use terminal instead of bash

components/dotenv.rst

@@ -51,7 +51,7 @@ Load a ``.env`` file in your PHP application via ``Dotenv::load()``::
 
 Given the following ``.env`` file content:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     # .env
     DB_USER=root
@@ -86,22 +86,22 @@ shell scripts:
 
 Add comments by prefixing them with ``#``:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     # Database credentials
     DB_USER=root
     DB_PASS=pass # This is the secret password
 
 Use environment variables in values by prefixing variables with ``$``:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     DB_USER=root
     DB_PASS=${DB_USER}pass # Include the user as a password prefix
 
 Embed commands via ``$()`` (not supported on Windows):
 
-.. code-block:: bash
+.. code-block:: terminal
 
     START_TIME=$(date)
 

components/phpunit_bridge.rst

@@ -565,7 +565,7 @@ the ``simple-phpunit`` if it is not provided.
 
 If you have installed the bridge through Composer, you can run it by calling e.g.:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     $ vendor/bin/simple-phpunit
 

configuration/micro_kernel_trait.rst

@@ -17,7 +17,7 @@ A Single-File Symfony Application
 Start with a completely empty directory. Get ``symfony/symfony`` as a dependency
 via Composer:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     $ composer require symfony/symfony
 
@@ -76,7 +76,7 @@ Next, create an ``index.php`` file that creates a kernel class and executes it::
 
 That's it! To test it, you can start the built-in web server:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     $ php -S localhost:8000
 
@@ -339,7 +339,7 @@ this:
 
 As before you can use PHP built-in server:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     cd web/
     $ php -S localhost:8000

frontend/assetic/asset_management.rst

@@ -11,7 +11,7 @@ Starting from Symfony 2.8, Assetic is no longer included by default in the
 Symfony Standard Edition. Before using any of its features, install the
 AsseticBundle executing this console command in your project:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     $ composer require symfony/assetic-bundle
 

performance.rst

@@ -199,7 +199,7 @@ in ``vendor/composer/autoload_classmap.php``.
 Execute this command to generate the class map (and make it part of your
 deployment process too):
 
-.. code-block:: bash
+.. code-block:: terminal
 
     $ composer dump-autoload --optimize --no-dev --classmap-authoritative
 

security/guard_authentication.rst

@@ -344,7 +344,7 @@ Finally, configure your ``firewalls`` key in ``security.yml`` to use this authen
 You did it! You now have a fully-working API token authentication system. If your
 homepage required ``ROLE_USER``, then you could test it under different conditions:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     # test with no token
     curl http://localhost:8000/
@@ -480,7 +480,7 @@ to cause a failure::
 In this case, since "ILuvAPIs" is a ridiculous API key, you could include an easter
 egg to return a custom message if someone tries this:
 
-.. code-block:: bash
+.. code-block:: terminal
 
     curl -H "X-AUTH-TOKEN: ILuvAPIs" http://localhost:8000/
     # {"message":"ILuvAPIs is not a real API key: it's just a silly phrase"}