Skip to content

Commit 75c97e2

Browse files
committed
Fixed couple typos
1 parent a197484 commit 75c97e2

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

Resources/doc/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -235,7 +235,7 @@ and customize it to fit your needs.
235235

236236
In order for Symfony's security component to use the FOSUserBundle, you must
237237
tell it to do so in the `security.yml` file. The `security.yml` file is where the
238-
basic configuration for the security for your application is contained.
238+
basic security configuration for your application is contained.
239239

240240
Below is a minimal example of the configuration necessary to use the FOSUserBundle
241241
in your application:
@@ -274,27 +274,27 @@ Under the `providers` section, you are making the bundle's packaged user provide
274274
service available via the alias `fos_userbundle`. The id of the bundle's user
275275
provider service is `fos_user.user_provider.username`.
276276

277-
Next, take a look at examine the `firewalls` section. Here we have declared a
277+
Next, take a look at and examine the `firewalls` section. Here we have declared a
278278
firewall named `main`. By specifying `form_login`, you have told the Symfony2
279279
framework that any time a request is made to this firewall that leads to the
280280
user needing to authenticate himself, the user will be redirected to a form
281281
where he will be able to enter his credentials. It should come as no surprise
282-
then that you have specified the user provider we declared earlier as the
282+
then that you have specified the user provider service we declared earlier as the
283283
provider for the firewall to use as part of the authentication process.
284284

285285
**Note:**
286286

287287
> Although we have used the form login mechanism in this example, the FOSUserBundle
288-
> user provider is compatible with many other authentication methods as well. Please
289-
> read the Symfony2 Security component documention for more information on the
288+
> user provider service is compatible with many other authentication methods as well.
289+
> Please read the Symfony2 Security component documention for more information on the
290290
> other types of authentication methods.
291291

292292
The `access_control` section is where you specify the credentials necessary for
293293
users trying to access specific parts of your application. The bundle requires
294294
that the login form and all the routes used to create a user and reset the password
295295
be available to unauthenticated users but use the same firewall as
296296
the pages you want to secure with the bundle. This is why you have specified that
297-
the any request matching the `/login` pattern or starting with `/register` or
297+
any request matching the `/login` pattern or starting with `/register` or
298298
`/resetting` have been made available to anonymous users. You have also specified
299299
that any request beginning with `/admin` will require a user to have the
300300
`ROLE_ADMIN` role.

0 commit comments

Comments
 (0)