[Development] Documentation typo fixes

[Sze Howe Koh]

On 7 February 2017 at 08:39, Ch'Gans <chgans at gna.org> wrote:
>
> Hi there,
>
> It's been a while that I notice some typos here and there in Qt5
> documentation (mainly qtbase), and i decided that i would start
> correcting them in the source code.
> Most of them are really straight forward, eg. in QGraphicsView::setTransform:
> "To simplify interation with items using a transformed view, ..."
> should be:
> "To simplify interaction with items using a transformed view, ..."
>
> It's just one example from this morning. Not a big of a deal, but
> documentation looks always nicer without typos.
>
> I would like to know to which branch should i target such "code
> review" on gerrit.
> Should it be "Current release", "Next release", "dev" or "master"?
> My gut feeling tells me "dev", so that from there, maintainers can
> decide if they want to propagate or not.
> Could someone confirm this?
>
> Thanks,
> Chris

Hi Chris,

Thank you for helping to fix typos.

See http://wiki.qt.io/Branch_Guidelines (Note: Qt module repositories
don't have a "master" branch)

Right now, the branches that accept documentation fixes are:

* 5.8 (stable branch)
* 5.9 (next release branch)
* dev (development branch)

Simply put, patches will merge from the top of the list to the bottom
of this list. For example, patches that go into "5.8" will eventually
be merged into "5.9", which in turn will eventually be merged into
"dev".

Typo fixes are not new features or major/risky changes, so they can go
into the stable branch ("5.8").


Regards,
Sze-Howe