docs: Style fixes for the contribution guidelines

This commit is contained in:
Emmanuele Bassi 2018-03-21 01:05:29 +00:00
parent 1cfa88ed91
commit fe45cf9c09

View File

@ -1,20 +1,20 @@
If you want to hack on the GTK+ project, you'll need to have the development If you want to hack on the GTK+ project, you'll need to have the development
tools appropriate for your operating system, including: tools appropriate for your operating system, including:
- Python 3.x - Python 3.x
- Meson - Meson
- Ninja - Ninja
- Gettext (19.7 or newer) - Gettext (19.7 or newer)
- a C99 compatible compiler - a C99 compatible compiler
Up-to-date instructions about developing GNOME applications and libraries Up-to-date instructions about developing GNOME applications and libraries
can be found here: can be found here:
https://developer.gnome.org * https://developer.gnome.org
Information about using GitLab with GNOME can be found here: Information about using GitLab with GNOME can be found here:
https://wiki.gnome.org/GitLab * https://wiki.gnome.org/GitLab
In order to get Git GTK+ installed on your system, you need to have the In order to get Git GTK+ installed on your system, you need to have the
required versions of all the GTK+ dependencies; typically, this means a required versions of all the GTK+ dependencies; typically, this means a
@ -60,4 +60,4 @@ $ git checkout -b your-branch
Once you've finished working on the bug fix or feature, push the branch Once you've finished working on the bug fix or feature, push the branch
to the Git repository and open a new merge request, to let the GTK to the Git repository and open a new merge request, to let the GTK
maintainers review your contribution. maintainers review your contribution.