Skip to content

[Contributing] consistent headlines #3828

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.

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

Merged
merged 1 commit into from
May 9, 2014
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions contributing/code/bc.rst
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Our Backwards Compatibility Promise
Our backwards Compatibility Promise
===================================

Ensuring smooth upgrades of your projects is our first priority. That's why
Expand Down Expand Up @@ -39,7 +39,7 @@ If you are using Symfony in your projects, the following guidelines will help
you to ensure smooth upgrades to all future minor releases of your Symfony
version.

Using Our Interfaces
Using our Interfaces
~~~~~~~~~~~~~~~~~~~~

All interfaces shipped with Symfony can be used in type hints. You can also call
Expand Down Expand Up @@ -101,7 +101,7 @@ backwards compatibility promise:

.. include:: _api_tagging.rst.inc

Using Our Classes
Using our Classes
~~~~~~~~~~~~~~~~~

All classes provided by Symfony may be instantiated and accessed through their
Expand Down
2 changes: 1 addition & 1 deletion contributing/code/patches.rst
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ Get the Symfony2 source code:
$ cd symfony
$ git remote add upstream git://github.com/symfony/symfony.git

Check that the current Tests pass
Check that the current Tests Pass
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Now that Symfony2 is installed, check that all unit tests pass for your
Expand Down
4 changes: 2 additions & 2 deletions contributing/community/releases.rst
Original file line number Diff line number Diff line change
Expand Up @@ -123,8 +123,8 @@ This results in very predictable dates and maintenance periods:
instance), you can automatically receive an email notification if you
subscribed on the `roadmap notification`_ page.

Backward Compatibility
----------------------
Backwards Compatibility
-----------------------

Our :doc:`Backwards Compatibility Promise </contributing/code/bc>` is very
strict and allows developers to upgrade with confidence from one minor version
Expand Down
4 changes: 2 additions & 2 deletions contributing/documentation/overview.rst
Original file line number Diff line number Diff line change
Expand Up @@ -187,7 +187,7 @@ about in the :doc:`/contributing/community/releases` section.
To keep up with the release process, the documentation team makes several
changes to the documentation at various parts of the lifecycle.

When a Release reaches "end of maintenance"
When a Release Reaches "End of Maintenance"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Every release will eventually reach its "end of maintenance". For details,
Expand All @@ -210,7 +210,7 @@ For this example, suppose version 2.1 has just reached its end of maintenance:
*after* the end of maintenance of this branch), will have no mentions of
the old version (e.g. 2.1).

When a new Branch is created for a Release
When a new Branch is Created for a Release
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

During the :ref:`stabilization phase <contributing-release-development>`, a
Expand Down