Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUGFIX] Fix typos in documentation #662

Merged
merged 1 commit into from
Nov 7, 2023
Merged

[BUGFIX] Fix typos in documentation #662

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/extension/structure.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ For the PHP package to be an extension you need a class
extending `\Symfony\Component\DependencyInjection\Extension\Extension` by
implementing the interface
`Symfony\Component\DependencyInjection\Extension\PrependExtensionInterface` we
can also add our ow configurations to our extension:
can also add our own configurations to our extension:

.. literalinclude:: _YourExtension.php
:language: php
Expand Down
8 changes: 4 additions & 4 deletions docs/extension/templates.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
Extending Templates
===================

Register the templates overrides in your extensions
Register the templates overrides in your extension's
:ref:`Extension class <extension_symfony>`:

.. literalinclude:: _YourExtension.php
Expand All @@ -15,8 +15,8 @@ Register the templates overrides in your extensions
:lineos:
:emphasize-lines: 29-35

It is recommended to always extend an existing template so that the base
templates twig files can be used as fallback for non-defined specific template
It is recommended to always extend an existing template so that the Twig files
of the base templates can be used as fallback for non-defined specific template
files.

In order to extend the default bootstrap theme, require the according base
Expand Down Expand Up @@ -46,7 +46,7 @@ To extend the base template (plain HTML) require `phpdocumentor/guides` in your
'themes' => ['mytheme' => dirname(__DIR__, 3) . '/resources/template'],
]);

You can now copy any twig file from the extended extensions and change it with
You can now copy any Twig file from the extended extensions and change it with
the full power of `Twig <https://twig.symfony.com/>`__.

Have a look at the `custom theme for TYPO3 Documentation <https://github.com/TYPO3-Documentation/typo3-docs-theme>`__
Expand Down
2 changes: 1 addition & 1 deletion docs/extension/text-roles.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ to introduce a new template in path :file:`resources/template/html/guides/inline
See also :ref:`basic-text-role`.

For more complex examples you can implement `\phpDocumentor\Guides\RestructuredText\TextRoles\TextRole`
and let the method `processNode` return a custom `\phpDocumentor\Guides\Nodes\InlineToken` if this token extends
and let the method `processNode` return a custom `\phpDocumentor\Guides\Nodes\InlineToken`. If this token extends
`\phpDocumentor\Guides\Nodes\GenericTextRoleToken` the template will be automatically resolved by the name of the type.
For more control rendering you can also implement your own token renderer.

Expand Down