Просмотр исходного кода

doc: Fix two typos in coding-style.txt

Signed-off-by: Niels Thykier <niels@thykier.net>
Signed-off-by: Guillem Jover <guillem@debian.org>
Niels Thykier лет назад: 14
Родитель
Сommit
d1670cfba0
1 измененных файлов с 2 добавлено и 2 удалено
  1. 2 2
      doc/coding-style.txt

+ 2 - 2
doc/coding-style.txt

@@ -28,12 +28,12 @@ Code should generally strive for clarity. Monster functions should be split
 into logical and small pieces.
 into logical and small pieces.
 
 
 Variable and function names should be generally descriptive, not needed
 Variable and function names should be generally descriptive, not needed
-for variables commonly used (for example and index inside a loop, etc),
+for variables commonly used (for example an index inside a loop, etc),
 acronyms should only be used if they are widely known externally or
 acronyms should only be used if they are widely known externally or
 inside the project. The names should separate logical concepts within
 inside the project. The names should separate logical concepts within
 with underscores.
 with underscores.
 
 
-On comments use UTF-8 characters for quotes, copyrigth symbols, etc.
+On comments use UTF-8 characters for quotes, copyright symbols, etc.
 
 
 On strings in code use simple or double quotes «''» «""». Not the unpaired
 On strings in code use simple or double quotes «''» «""». Not the unpaired
 ones «`'». Strings marked for translation, should only be fixed if there's
 ones «`'». Strings marked for translation, should only be fixed if there's