Permalink
Browse files

Merge pull request #713 from maschmann/maschmann/coding_guidelines

Spelling fixes for guidelines
  • Loading branch information...
CraigChilds94 committed Sep 23, 2014
2 parents 308c0b6 + be84a51 commit 077ee466981c340b311418ac946d7d25c028d8fd
Showing with 2 additions and 2 deletions.
  1. +2 −2 contributing.md
@@ -32,7 +32,7 @@ If your fork is taking a while to get merged, you might end up getting behind An
### When coding, always use coding standards
If you're familiar with open source software, you probably know how important coding guidelines and standards are. Most common are (in order of appearance) PEAR, Zend(Framework) and [PSR-1](http://www.php-fig.org/psr/psr-1)/[PSR-2](http://www.php-fig.org/psr/psr-2).
Since the [PHP-FIG](http://www.php-fig.org) and their standards gain more and more followers and anchor uses composer, which supports PSR-0 and PSR-4, all code should follow [PSR-1](http://www.php-fig.org/psr/psr-1) and [PSR-2](http://www.php-fig.org/psr/psr-2).
More help on best practices for php development can be found on [php the right way](http://www.phptherightway.com).
Since the [PHP-FIG](http://www.php-fig.org) and their standards gain more and more followers and Anchor uses composer, which supports PSR-0 and PSR-4, all code should follow [PSR-1](http://www.php-fig.org/psr/psr-1) and [PSR-2](http://www.php-fig.org/psr/psr-2).
More help on best practices for PHP development can be found on [PHP the right way](http://www.phptherightway.com).
When working on a file, always enforce coding standards for the whole file. This increases the consistency of the code with every contribution!

0 comments on commit 077ee46

Please sign in to comment.