Use Vale on 'quick tour', 'create framework' and getting started sections

Author: wouterj

.vale.ini

@@ -4,6 +4,11 @@ Packages = Microsoft, write-good
 Vocab = Symfony
 
 [*]
-BasedOnStyles = Vale, Microsoft, write-good
-BlockIgnores = (?s) *(\.\. configuration-block::)
+BasedOnStyles = Vale, Microsoft, write-good, Symfony
+BlockIgnores = (?s) *(\.\. (configuration-block|code-block)::[^\n]+(\n\s[^\n]+)+)
 TokenIgnores = (:ref:`.*`)
+
+Microsoft.Headings = NO
+Microsoft.Foreign = NO
+Microsoft.Quotes = NO
+Microsoft.Contractions = NO

.vale/Symfony/Headings.yml

@@ -0,0 +1,6 @@
+extends: capitalization
+message: "'%s' should be in title case"
+level: warning
+scope: heading
+match: $title
+style: Chicago

.vale/config/vocabularies/Symfony/accept.txt

@@ -1,7 +1,32 @@
 Symfony
-namespace
-autowiring
-autowired
-boolean
-stderr
-config
+Ctype
+iconv
+Tokenizer
+Monolog
+nginx
+Laravel
+ezPublish
+PHPUnit
+Xdebug
+webpack
+(?i)autocompletes
+(?i)autoload(ing|ed)
+(?i)autoloader
+(?i)autowir(ing|ed)
+(?i)autowire
+(?i)auto-(installing|escaping)
+(?i)boolean
+(?i)charset
+(?i)config
+(?i)env
+(?i)hardcode(d|s)
+(?i)hasser
+(?i)inlined
+(?i)isser
+(?i)namespace
+(?i)profiler
+(?i)reusability
+(?i)stderr
+(?i)uncomment
+(?i)unvalidated
+(?i)validator

configuration.rst

@@ -895,9 +895,9 @@ override environment variables defined in ``.env`` files.
 Configuring Environment Variables in Production
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-In production, the ``.env`` files are also parsed and loaded on each request. So
-the easiest way to define env vars is by creating a ``.env.local`` file on your
-production server(s) with your production values.
+In production, the ``.env`` files are also parsed and loaded on each request.
+The easiest way to define env vars is by creating a ``.env.local`` file on your
+production servers with your production values.
 
 To improve performance, you can optionally run the ``dump-env`` Composer command:
 

controller.rst

@@ -104,7 +104,7 @@ Generating URLs
 ~~~~~~~~~~~~~~~
 
 The :method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\AbstractController::generateUrl`
-method is just a helper method that generates the URL for a given route::
+method is just a helper method that generates the URL of a given route::
 
     $url = $this->generateUrl('app_lucky_number', ['max' => 10]);
 
@@ -458,7 +458,7 @@ In Symfony, a controller is required to return a ``Response`` object::
     $response->headers->set('Content-Type', 'text/css');
 
 To facilitate this, different response objects are included to address different
-response types.  Some of these are mentioned below. To learn more about the
+response types. Some of these are mentioned below. To learn more about the
 ``Request`` and ``Response`` (and different ``Response`` classes), see the
 :ref:`HttpFoundation component documentation <component-http-foundation-request>`.
 

create_framework/dependency_injection.rst

@@ -65,7 +65,7 @@ reporting turned on and errors displayed in the browser to ease debugging::
 environment. Having two different front controllers gives you the opportunity
 to have a slightly different configuration for each of them.
 
-So, moving code from the front controller to the framework class makes our
+Moving code from the front controller to the framework class makes our
 framework more configurable, but at the same time, it introduces a lot of
 issues:
 

create_framework/http_foundation.rst

@@ -22,7 +22,7 @@ it suffers from a few problems::
     printf('Hello %s', $name);
 
 First, if the ``name`` query parameter is not defined in the URL query string,
-you will get a PHP warning; so let's fix it::
+you will get a PHP warning; let's fix it::
 
     // framework/index.php
     $name = $_GET['name'] ?? 'World';
@@ -93,8 +93,8 @@ reading this book now and go back to whatever code you were working on before.
 Going OOP with the HttpFoundation Component
 -------------------------------------------
 
-Writing web code is about interacting with HTTP. So, the fundamental
-principles of our framework should be around the `HTTP specification`_.
+Writing web code is about interacting with HTTP. The fundamental principles
+of our framework should be around the `HTTP specification`_.
 
 The HTTP specification describes how a client (a browser for instance)
 interacts with a server (our application via a web server). The dialog between
@@ -261,7 +261,7 @@ explicitly trust your reverse proxies by calling ``setTrustedProxies()``::
         // the client is a known one, so give it some more privilege
     }
 
-So, the ``getClientIp()`` method works securely in all circumstances. You can
+The ``getClientIp()`` method works securely in all circumstances. You can
 use it in all your projects, whatever the configuration is, it will behave
 correctly and safely. That's one of the goals of using a framework. If you were
 to write a framework from scratch, you would have to think about all these

create_framework/http_kernel_controller_resolver.rst

@@ -1,4 +1,4 @@
-The HttpKernel Component: the Controller Resolver
+The HttpKernel Component: The Controller Resolver
 =================================================
 
 You might think that our framework is already pretty solid and you are

create_framework/routing.rst

@@ -157,7 +157,7 @@ With this knowledge in mind, let's write the new version of our framework::
 
     $response->send();
 
-There are a few new things in the code:
+This code has a few new things:
 
 * Route names are used for template names;
 

create_framework/unit_testing.rst

@@ -196,7 +196,7 @@ controller. We check that the response status is 200 and that its content is
 the one we have set in the controller.
 
 To check that we have covered all possible use cases, run the PHPUnit test
-coverage feature (you need to enable `XDebug`_ first):
+coverage feature (you need to enable `Xdebug`_ first):
 
 .. code-block:: terminal