ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-10-03 23:14:02 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Fix various typos in markdown documentation

Browse source
This commit is contained in:
John Barker 2014-02-10 23:00:19 +00:00
commit 1f4b91575b
4 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

8
CODING_GUIDELINES.md
View file

@ -6,7 +6,7 @@ Hi! Thanks for interest in contributing to Ansible.
Here are some guidelines for contributing code. The purpose of this document are to establish what we're looking for in code contributions, and to make sure
new contributions know some of the conventions that we've been using.
We don't think much of this should be too strange to readers familar with contributing to Python projects, though it helps if we all get on the same page.
We don't think much of this should be too strange to readers familiar with contributing to Python projects, though it helps if we all get on the same page.
Language
========
@ -44,7 +44,7 @@ Shebang Lines
=============
* /usr/bin/scripts should start with '/usr/bin/env python'
* module code should still use '/usr/bin/python' as this is replaced automatically by 'ansible_python_interpeter', see the FAQ in the docs for more info.
* module code should still use '/usr/bin/python' as this is replaced automatically by 'ansible_python_interpreter', see the FAQ in the docs for more info.
Comments
========
@ -58,7 +58,7 @@ Comments
Classes
=======
* With the exception of module code (where inline is better), it is deseriable to see classes in their own files.
* With the exception of module code (where inline is better), it is desirable to see classes in their own files.
* Classes should generally not cause side effects as soon as they are instantiated, move meaningful behavior to methods rather than constructors.
Functions and Methods
@ -262,7 +262,7 @@ To test if something is a string, consider that it may be unicode.
if type(x) == str:
# yes
if isintance(x, basestring):
if isinstance(x, basestring):
Cleverness
==========