remove indention from the whitelist.

Signed-off-by: Tomoya Fujita <[email protected]>

codespell_whitelist.txt

@@ -1,2 +1 @@
 empy
-indention

source/The-ROS2-Project/Contributing/Code-Style-Language-Versions.rst

@@ -166,9 +166,9 @@ Pointer Syntax Alignment
 Class Privacy Keywords
 ~~~~~~~~~~~~~~~~~~~~~~
 
-* Do not put 1 space before ``public:``, ``private:``, or ``protected:``, it is more consistent for all indentions to be a multiple of 2
+* Do not put 1 space before ``public:``, ``private:``, or ``protected:``, it is more consistent for all indentations to be a multiple of 2
 
-  * rationale: most editors don't like indentions which are not a multiple of the (soft) tab size
+  * rationale: most editors don't like indentations which are not a multiple of the (soft) tab size
   * Use zero spaces before ``public:``, ``private:``, or ``protected:``, or 2 spaces
   * If you use 2 spaces before, indent other class statements by 2 additional spaces
   * Prefer zero spaces, i.e. ``public:``, ``private:``, or ``protected:`` in the same column as the class
@@ -254,7 +254,7 @@ This is **not** OK:
    }
 
 
-Use open braces rather than excessive indention, e.g. for distinguishing constructor code from constructor initializer lists
+Use open braces rather than excessive indentation, e.g. for distinguishing constructor code from constructor initializer lists
 
 This is OK:
 
@@ -364,7 +364,7 @@ Since there is not an existing CMake style guide we will define our own:
 * Use ``snake_case`` identifiers (variables, functions, macros).
 * Use empty ``else()`` and ``end...()`` commands.
 * No whitespace before ``(``\ 's.
-* Use two spaces of indention, do not use tabs.
+* Use two spaces of indentation, do not use tabs.
 * Do not use aligned indentation for parameters of multi-line macro invocations. Use two spaces only.
 * Prefer functions with ``set(PARENT_SCOPE)`` to macros.
 * When using macros prefix local variables with ``_`` or a reasonable prefix.