Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace the term rules with more accurate wording #79

Merged
merged 1 commit into from
Mar 25, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -336,8 +336,8 @@ is *how* this indentation of 4 columns is achieved. It may be 4 consequent space
a single tab with width equal to 4, or two tabs with width equal to 2.

This is when ``indent_style`` comes into picture. It specifies what character should be used **whenever possible** in order to
achieve the indentation size specified in ``indent_size``. To fully understand what "whenever possible" actually means, lets
assume that the editorconfig rules are specified for the file above:
achieve the indentation size specified in ``indent_size``. To fully understand what "whenever possible" actually means, let's
consider the following EditorConfig file living in the same directory as the file above:

.. code-block:: ini

Expand All @@ -353,7 +353,7 @@ indented with one tab, and one space**. That is because by placing one tab we're
placing the 2 consequent tabs we're overreaching. Therefore, although ``indent_style`` is ``tab``, we still have to supplement
with one space character to fulfill the requirement.

For another example, if we have the following EditorConfig rules defined:
For another example, if we have the following EditorConfig file:

.. code-block:: ini

Expand Down