8000 [best practices] mostly typos by talitakz · Pull Request #6348 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

[best practices] mostly typos #6348

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

Closed
wants to merge 2 commits into from
Closed

[best practices] mostly typos #6348

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0f80bb6
[best practices] mostly typos
talitakz Feb 15, 2016
fe2e1ed
changes according to comments after pull request
talitakz Mar 11, 2016
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
Prev Previous commit
changes according to comments after pull request
  • Loading branch information
@talitakz
talitakz committed Mar 11, 2016
commit fe2e1eddb808532e447c3d73cb3198f115147c61
4 changes: 2 additions & 2 deletions best_practices/controllers.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,14 +73,14 @@ Template Configuration

.. best-practice::

Don't use the ``@Template()`` annotation to configure the template used by
Don't use the ``@Template`` annotation to configure the template used by
the controller.

The ``@Template`` annotation is useful, but also involves some magic. We
don't think its benefit is worth the magic, and so recommend against using
it.

Most of the time, ``@Template()`` is used without any parameters, which makes
Most of the time, ``@Template`` is used without any parameters, which makes
it more difficult to know which template is being rendered. It also makes
it less obvious to beginners that a controller should always return a Response
object (unless you're using a view layer).
Expand Down
2 changes: 1 addition & 1 deletion best_practices/forms.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ thing in one line to rendering each part of each field independently. The
best way depends on how much customization you need.

One of the simplest ways - which is especially useful during development -
is to render the form tags and use Twig ``form_widget()`` function to render
is to render the form tags and use ``form_widget()`` function to render
all of the fields:

.. code-block:: html+twig
Expand Down
0