Do we really want Boolean? I really don't like it as it's inconsistent.

@wouterj I think it make sense in terms that it is derived from George Boole's name. We also usedBoolean in quite a lot of places in the reference for option types. Though I don't have any strong feelings about this. If you all think thatboolean feels more natural, I'll revert the changes and convert uppercased occurences with lowercased ones.

By the way, why do we useBoolean in the reference at all and don't usebool like the Symfoy code base does? Is it just for historical reasons?

@xabbuh I agree with@wouterj: even ifBoolean is the correct term, most developers use it asboolean and treat it as a common word.

Seems we have a majority forboolean instead ofBoolean then. :) Have replaced them accordingly.

@xabbuh the code changed this year tobool instead ofBoolean (that's where the capitialized boolean in the docs come from), to make their types compatible with Hack (http://docs.hhvm.com/manual/en/hack.annotations.types.php).

I don't think bool is as clear as boolean, that's why I propose to keep using boolean instead of bool

@wouterj Thanks for the explanation. So, should we now keep lowercasedboolean everywhere or switch it back toBoolean in the reference and useboolean in texts only?

I think we should useboolean (lowercased) everywhere.

This is ready to be reviewed now. I've kept different commits for each item of the task list so that you can review each step on its own.

However, there are two changes I'm not completely happy with:

• Unifying occurrences of Symfony framework and Symfony Framework to always use the latter on is probably a good idea. But we also have a lot of occurrences of "Symfony full-stack Framework" now which looks a bit weird. Should we keep it anyway? Or replace it with something like "full-stack Symfony Framework" or "Symfony Full-Stack Framework"?
• I don't like using uppercase letters for "Dependency Injection". Why don't we write "dependency injection container", "dependency injection tags" and "dependency injection extension class" while keeping uppercase letters only for the "DependencyInjection component"?

@xabbuh regarding your questions:

1. I prefer using this variant:full-stack Symfony Framework
2. I agree with you about lowercasingdependency injection except when referring to the component.

Do you think this PR could be merged anytime soon? It looks like we're very close thanks to your great work and it's sad to see these nice improvements pending to be merged. Thanks.

@javiereguiluz This can be merged once we agree on all the changes. :) Though I'm fine with splitting it in several PRs if there are some things that should be discussed while others may be settled.

@wouterj@weaverryan What do you think?

+1 for Symfony Full-Stack Framework
+1 for lowercase dependency injection and only capitialized when talking about the component

Btw, thsi also needs a rebase.

This PR still contains the boolean mix up.

I rebased and finally fixed the boolean/Boolean mix up.

Let's merge this one to avoid more conflicts :)

WOW@xabbuh. And not even any conflicts :). Thanks for the long work on this!