minor #12945 Move method and class (OskarStark)

This PR was merged into the 3.4 branch.

Discussion
----------

Move method and class

It reads more natural to me.

I would check the following branches if you agree and in this case we could add a Doctor rule.

Cheers

Commits
-------

8bffa06 Move method and class

Author: OskarStark

components/console/single_command_tool.rst

@@ -29,7 +29,7 @@ it is possible to remove this need by declaring a single command application::
         ->setDefaultCommand('echo', true) // Single command application
         ->run();
 
-The method :method:`Symfony\\Component\\Console\\Application::setDefaultCommand`
+The :method:`Symfony\\Component\\Console\\Application::setDefaultCommand` method
 accepts a boolean as second parameter. If true, the command ``echo`` will then
 always be used, without having to pass its name.
 

components/options_resolver.rst

@@ -297,7 +297,7 @@ been set::
         }
     }
 
-The method :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::getMissingOptions`
+The :method:`Symfony\\Component\\OptionsResolver\\OptionsResolver::getMissingOptions` method
 lets you access the names of all missing options.
 
 Type Validation

components/routing.rst

@@ -28,7 +28,7 @@ Usage
 
 In order to set up a basic routing system you need three parts:
 
-* A :class:`Symfony\\Component\\Routing\\RouteCollection`, which contains the route definitions (instances of the class :class:`Symfony\\Component\\Routing\\Route`)
+* A :class:`Symfony\\Component\\Routing\\RouteCollection`, which contains the route definitions (instances of the :class:`Symfony\\Component\\Routing\\Route` class)
 * A :class:`Symfony\\Component\\Routing\\RequestContext`, which has information about the request
 * A :class:`Symfony\\Component\\Routing\\Matcher\\UrlMatcher`, which performs the mapping of the request to a single route
 

components/security/authentication.rst

@@ -100,10 +100,10 @@ Authentication Providers
 
 Each provider (since it implements
 :class:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface`)
-has a method :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::supports`
+has a :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::supports` method
 by which the ``AuthenticationProviderManager``
 can determine if it supports the given token. If this is the case, the
-manager then calls the provider's method :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::authenticate`.
+manager then calls the provider's :method:`Symfony\\Component\\Security\\Core\\Authentication\\Provider\\AuthenticationProviderInterface::authenticate` method.
 This method should return an authenticated token or throw an
 :class:`Symfony\\Component\\Security\\Core\\Exception\\AuthenticationException`
 (or any other exception extending it).

reference/constraints/File.rst

@@ -6,7 +6,7 @@ Validates that a value is a valid "file", which can be one of the following:
 * A string (or object with a ``__toString()`` method) path to an existing
   file;
 * A valid :class:`Symfony\\Component\\HttpFoundation\\File\\File` object
-  (including objects of class :class:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile`).
+  (including objects of :class:`Symfony\\Component\\HttpFoundation\\File\\UploadedFile` class).
 
 This constraint is commonly used in forms with the :doc:`FileType </reference/forms/types/file>`
 form field.

validation.rst

@@ -115,7 +115,7 @@ on the ``validator`` service (which implements :class:`Symfony\\Component\\Valid
 The job of the ``validator`` is easy: to read the constraints (i.e. rules)
 of a class and verify if the data on the object satisfies those
 constraints. If validation fails, a non-empty list of errors
-(class :class:`Symfony\\Component\\Validator\\ConstraintViolationList`) is
+(:class:`Symfony\\Component\\Validator\\ConstraintViolationList` class) is
 returned. Take this simple example from inside a controller::
 
     // ...

workflow.rst

@@ -391,7 +391,7 @@ This means that each event has access to the following information:
 
         The ``getWorkflowName()`` method was introduced in Symfony 3.3.
 
-For Guard Events, there is an extended class :class:`Symfony\\Component\\Workflow\\Event\\GuardEvent`.
+For Guard Events, there is an extended :class:`Symfony\\Component\\Workflow\\Event\\GuardEvent` class.
 This class has two more methods:
 
 :method:`Symfony\\Component\\Workflow\\Event\\GuardEvent::isBlocked`