diff --git a/cookbook/bundles/extension.rst b/cookbook/bundles/extension.rst index 32c837b333e..105f048c798 100644 --- a/cookbook/bundles/extension.rst +++ b/cookbook/bundles/extension.rst @@ -21,7 +21,7 @@ as integration of other related components: framework: # ... - form: true + form: true .. code-block:: xml @@ -33,7 +33,7 @@ as integration of other related components: $container->loadFromExtension('framework', array( // ... - 'form' => true, + 'form' => true, // ... )); @@ -494,9 +494,10 @@ be output to the console in yaml. As long as your bundle's configuration is located in the standard location (``YourBundle\DependencyInjection\Configuration``) and does not have a -``__constructor()`` it will work automatically. If you have a something -different your ``Extension`` class will have to override the -``Extension::getConfiguration()`` method. Have it return an instance of your +``__construct()`` it will work automatically. If you have something +different, your ``Extension`` class must override the +:method:`Extension::getConfiguration() ` +method and return an instance of your ``Configuration``. Comments and examples can be added to your configuration nodes using the @@ -548,9 +549,9 @@ When creating an extension, follow these simple conventions: * The extension should provide an XSD schema. If you follow these simple conventions, your extensions will be registered -automatically by Symfony2. If not, override the Bundle -:method:`Symfony\\Component\\HttpKernel\\Bundle\\Bundle::build` method in -your bundle:: +automatically by Symfony2. If not, override the +:method:`Bundle::build() ` +method in your bundle:: // ... use Acme\HelloBundle\DependencyInjection\UnconventionalExtensionClass;