- Change non-existant English word with something understandable :-)

git-svn-id: svn://svn.gna.org/svn/sgpemv2/trunk@245 3ecf2c5c-341e-0410-92b4-d18e462d057c
This commit is contained in:
tchernobog 2006-01-28 20:42:20 +00:00
parent 4cad356657
commit e45d40eaff
1 changed files with 4 additions and 4 deletions

View File

@ -70,7 +70,7 @@ Free Documentation License''.
* Writing documentation:: How to write formal documents
for draft approval
* Coding style:: Here there are the rules you should abid
* Coding style:: Here there are the rules you should conform
to when working on SGPEM
* Committing changes:: Some notes on how we keep our
@ -334,7 +334,7 @@ number of pages.
@end itemize
To make it easier to abid to these rules, please remember to inherit
To make it easier to abide these rules, please remember to inherit
from the template document. It lays down a foundation for all
the style guidelines mentioned above.
@ -556,7 +556,7 @@ Usually it's the same person as the assignee.
In this chapter we explore some self-imposed coding standards
we tried to follow when coding SGPEM.
If you plan to extend it in any way, you should abid to the
If you plan to extend it in any way, you should conform to the
guidelines explained thereafter.
@menu
@ -1336,7 +1336,7 @@ the ML.
Most discussions start with a draft, like this. The talking then goes on
amendating the document and, when no-one opposes it anymore, the draft is
marked as an approved guideline, and everybody is meant to (as strictly
as possible) abide to it.
as possible) conform to it.
Exceptions or revisions to guidelines due to a rework done by some other
process pertain to the @acronym{KA,Knowledge Area} of