upstream

2 files changed, 4 insertions, 4 deletions

diff --git a/admin/grammars/c.by b/admin/grammars/c.by
index 1797827679b..004f0b5f30f 100644
--- a/admin/grammars/c.by
+++ b/admin/grammars/c.by
@@ -566,7 +566,7 @@ template-type
     (TYPE-TAG $2 "class" nil nil )
   | STRUCT symbol
     (TYPE-TAG $2 "struct" nil nil )
- ;; TODO: Klaus Berndl: For the moment is is ok, that we parse the C++
+ ;; TODO: Klaus Berndl: For the moment it is ok, that we parse the C++
  ;; keyword typename as a class....
   | TYPENAME symbol
     (TYPE-TAG $2 "class" nil nil)
@@ -734,7 +734,7 @@ builtintype
 
 ;; Klaus Berndl: This parses also nonsense like "const volatile int
 ;; const volatile const const volatile a ..." but IMHO nobody writes
-;; such code. Normaly we shoud define a rule like typeformbase-mode
+;; such code. Normally we should define a rule like typeformbase-mode
 ;; which exactly defines the different allowed cases and combinations
 ;; of declmods (minus the CVDECLMOD) typeformbase and cv-declmods so
 ;; we could recognize more invalid code but IMHO this is not worth the
@@ -1105,7 +1105,7 @@ fun-or-proto-end
     ( t )
   | semantic-list
     ( nil )
- ;; Here is an anoying feature of C++ pure virtual methods
+ ;; Here is an annoying feature of C++ pure virtual methods
   | EQUAL ZERO SEMICOLON
     ( :pure-virtual-flag )
   | fun-try-end
diff --git a/admin/grammars/python.wy b/admin/grammars/python.wy
index a0af813e5e8..b30305ee78a 100644
--- a/admin/grammars/python.wy
+++ b/admin/grammars/python.wy
@@ -828,7 +828,7 @@ paren_classes
   ;
 
 ;; In general, the base class can be specified by a general expression
-;; which evalue to a class object, i.e., base classes are not just names!
+;; which evaluates to a class object, i.e., base classes are not just names!
 ;; However base classes are names in most cases.  Thus the
 ;; non-terminals below work only with simple names.  Even if the
 ;; parser can parse general expressions, I don't see much benefit in