Skip to content

Commit 71f6902

Browse files
Apply suggestions from code review
Co-authored-by: Revathy Venugopal <[email protected]>
1 parent 2ee7674 commit 71f6902

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

doc/source/coding-style/formatting-tools.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -280,20 +280,20 @@ the `pre-commit.ci`_ tool provides some additional features:
280280

281281
- It is free for public projects.
282282
- It is compatible with any CI provider.
283-
- It ensures that the hooks versions are up to date.
283+
- It ensures that hook versions are up to date.
284284
- Any changes performed by the hooks are committed back to the repository.
285-
- Reduces the time spent running CI by caching the hooks used.
285+
- It reduces CI run times by caching the hooks used.
286286

287-
To use the `pre-commit.ci`_ tool, you must have a ``.pre-commit-config.yaml`` for your repository. Next,
287+
To use the `pre-commit.ci`_ tool, you must have a ``.pre-commit-config.yaml`` file for your repository. Next,
288288
you should request the `PyAnsys Core team <pyansys_core_email_>`_ to enable the `pre-commit.ci`_ tool for your
289289
repository.
290290

291291
.. note::
292292

293293
The `pre-commit.ci`_ tool is not available for private repositories.
294294

295-
From the PyAnsys ecosystem, it is strongly recommended to use the `pre-commit.ci`_ tool in your project. It is a
296-
great way to ensure that your code is compliant with the code style guidelines of the PyAnsys ecosystem.
295+
The PyAnsys ecosystem strongly recommends using the `pre-commit.ci`_ tool in your project. It is a
296+
great way to ensure that your code is compliant with the code style guidelines set by the PyAnsys ecosystem.
297297

298298
Using ``pre-commit.ci`` with conventional commits
299299
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

0 commit comments

Comments
 (0)