symfony
diff --git a/‎components/property_access/introduction.rst
Copy file name to clipboardExpand all lines: components/property_access/introduction.rst
+6-8Lines changed: 6 additions & 8 deletions b/‎components/property_access/introduction.rst
Copy file name to clipboardExpand all lines: components/property_access/introduction.rst
+6-8Lines changed: 6 additions & 8 deletions
@@ -117,7 +117,7 @@ property name (``first_name`` becomes ``FirstName``) and prefixes it with
     var_dump($accessor->getValue($person, 'first_name')); // 'Wouter'
 
 You can override the called getter method using metadata (i.e. annotations or
-configuration files). see `Custom method calls and virtual properties in a class`_
+configuration files). See `Custom method calls and virtual properties in a class`_.
 
 Using Hassers/Issers
 ~~~~~~~~~~~~~~~~~~~~
@@ -310,7 +310,7 @@ see `Enable other Features`_.
     var_dump($person->getWouter()); // array(...)
 
 You can override the called setter method using metadata (i.e. annotations or
-configuration files). see `Custom method calls and virtual properties in a class`_
+configuration files). See `Custom method calls and virtual properties in a class`_.
 
 Checking Property Paths
 -----------------------
@@ -375,7 +375,7 @@ Custom method calls and virtual properties in a class
 -----------------------------------------------------
 
 Sometimes you may not want the component to guess which method has to be called
-when reading or writing properties. This is specially interesting when property
+when reading or writing properties. This is especially interesting when property
 names are not in English or its singularization is not properly detected.
 
 For those cases you can add metadata to the class being accessed so that the
@@ -625,16 +625,14 @@ Or you can pass parameters directly to the constructor (not the recommended way)
 
 If you need to enable metadata processing (see
 `Custom method calls and virtual properties in a class`_) you must instantiate
-a :class:`Symfony\\Componente\\PropertyAcces\\Mapping\\Factory\\MetadataFactoryInterface`
+a :class:`Symfony\\Component\\PropertyAcces\\Mapping\\Factory\\MetadataFactoryInterface`
 and use the method `setMetadataFactory` on the
 :class:`Symfony\\Component\\PropertyAccess\\PropertyAccessorBuilder`. Bundled with
 the component you can find
 a `MetadataFactory` class that supports different kind of loaders (annotations,
-YAML and YML files) called :class:`
-Symfony\\Componente\\PropertyAcces\\Mapping\\Factory\\LazyLoadingMetadataFactory`.
+YAML and YML files) called :class:`Symfony\\Component\\PropertyAcces\\Mapping\\Factory\\LazyLoadingMetadataFactory`.
 
-Its constructor needs a :class:`
-Symfony\\Component\\PropertyAccess\\Mapping\\Loader\\LoaderInterface` which specifies
+Its constructor needs a :class:`Symfony\\Component\\PropertyAccess\\Mapping\\Loader\\LoaderInterface` which specifies
 the source of the metadata information. You can also use a PSR6 compliant cache
 as the second parameter passing a :class:`Psr\\Cache\\CacheItemPoolInterface`
 reference.