moar cleanups
diff --git a/examples/explore_ast.py b/examples/explore_ast.py
index f6be329..6d3e70c 100644
--- a/examples/explore_ast.py
+++ b/examples/explore_ast.py
@@ -9,7 +9,7 @@
# information from the AST.
# It helps to have the pycparser/_c_ast.cfg file in front of you.
#
-# Copyright (C) 2008-2011, Eli Bendersky
+# Copyright (C) 2008-2013, Eli Bendersky
# License: BSD
#-----------------------------------------------------------------
from __future__ import print_function
@@ -103,8 +103,7 @@
# The body is of FuncDef is a Compound, which is a placeholder for a block
# surrounded by {} (You should be reading _c_ast.cfg parallel to this
-# explanation and seeing these things by your own eyes).
-#
+# explanation and seeing these things with your own eyes).
# Let's see the block's declarations:
#
function_body = ast.ext[2].body
@@ -117,7 +116,6 @@
# We can see a single variable declaration, i, declared to be a simple type
# declaration of type 'unsigned int', followed by statements.
-#
# block_items is a list, so the third element is the For statement:
#
@@ -150,17 +148,14 @@
#~ while_cond.right.show()
#
-# That's it for the example. I hope you now see how easy it is to
-# explore the AST created by pycparser. Although on the surface it
-# is quite complex and has a lot of node types, this is the
-# inherent complexity of the C language every parser/compiler
-# designer has to cope with.
-# Using the tools provided by the c_ast package it's easy to
-# explore the structure of AST nodes and write code that processes
-# them.
-# Specifically, see the cdecl.py example for a non-trivial
-# demonstration of what you can do by recursively going through
-# the AST.
+# That's it for the example. I hope you now see how easy it is to explore the
+# AST created by pycparser. Although on the surface it is quite complex and has
+# a lot of node types, this is the inherent complexity of the C language every
+# parser/compiler designer has to cope with.
+# Using the tools provided by the c_ast package it's easy to explore the
+# structure of AST nodes and write code that processes them.
+# Specifically, see the cdecl.py example for a non-trivial demonstration of what
+# you can do by recursively going through the AST.
#
diff --git a/pycparser/_c_ast.cfg b/pycparser/_c_ast.cfg
index a8e33ff..2596de6 100644
--- a/pycparser/_c_ast.cfg
+++ b/pycparser/_c_ast.cfg
@@ -2,7 +2,7 @@
# pycparser: _c_ast.cfg
#
# Defines the AST Node classes used in pycparser.
-#
+#
# Each entry is a Node sub-class name, listing the attributes
# and child nodes of the class:
# <name>* - a child node
@@ -63,7 +63,7 @@
DoWhile: [cond*, stmt*]
-# Represents the ellipsis (...) parameter in a function
+# Represents the ellipsis (...) parameter in a function
# declaration
#
EllipsisParam: []
@@ -90,11 +90,11 @@
#
ExprList: [exprs**]
-# This is the top of the AST, representing a single C file (a
-# translation unit in K&R jargon). It contains a list of
+# This is the top of the AST, representing a single C file (a
+# translation unit in K&R jargon). It contains a list of
# "external-declaration"s, which is either declarations (Decl),
# Typedef or function definitions (FuncDef).
-#
+#
FileAST: [ext**]
# for (init; cond; next) stmt
@@ -111,7 +111,7 @@
FuncDecl: [args*, type*]
# Function definition: a declarator for the function name and
-# a body, which is a compound statement.
+# a body, which is a compound statement.
# There's an optional list of parameter declarations for old
# K&R-style definitions
#