Skip to content
This repository was archived by the owner on Sep 16, 2021. It is now read-only.

Commit 9a91013

Browse files
committed
add note on traits and more corrections
1 parent 4176f19 commit 9a91013

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

bundles/seo/seo_aware.rst

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,9 @@ the ``SeoMetadata``::
3030
}
3131
}
3232

33+
If you are using PHP5.4+ you may also benefit from using the trait ``SeoAwareTrait``
34+
to plug these behavior into your model.
35+
3336
Now you can set some SEO data for this ``Page`` using the metadata::
3437

3538
use Acme\SiteBundle\Document\Page;
@@ -220,7 +223,7 @@ object:
220223
</entity>
221224
</doctrine-mapping>
222225
223-
You can also choose to put the ``SeoMetadata`` class into a seperate table. To
226+
You can also choose to put the ``SeoMetadata`` class into a separate table. To
224227
do this, you have to enable ORM support just like you enabled PHPCR enabled
225228
above and add a OneToOne or ManyToOne relation between the content entity and
226229
the ``SeoMetadata`` entity.
@@ -233,15 +236,15 @@ form type can be used in forms to edit the ``SeoMetadata`` object.
233236

234237
.. caution::
235238

236-
The bundles requires the `BurgovKeyValueFormBundle`_ when using the form
239+
The bundle requires the `BurgovKeyValueFormBundle`_ when using the form
237240
type. Make sure you install and enable it.
238241

239242
Sonata Admin Integration
240243
------------------------
241244

242245
Besides providing a form type, the bundle also provides a Sonata Admin
243246
Extension. This extension adds a field for the ``SeoMetadata`` when an admin
244-
edits an objec that implements the ``SeoAwareInterface`` in the Sonata Admin
247+
edits an object that implements the ``SeoAwareInterface`` in the Sonata Admin
245248
panel.
246249

247250
.. caution::

0 commit comments

Comments
 (0)