Skip to content

Commit 644b4e1

Browse files
authored
docs: correct two typos in the contribution guide (#1640)
docs: fix contribution guide typos
1 parent a602f78 commit 644b4e1

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎.github/CONTRIBUTING.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ We recommend using the Python version from the `.python-version-default` file in
7777

7878
We use a fully-locked development environment using [*uv*](https://docs.astral.sh/uv/) so the easiest way to get started is to [install *uv*] and you can run `uv run pytest` to run the tests immediately.
7979

80-
I you'd like a traditional virtual environment, you can run `uv sync --python=$(cat .python-version-default)` and it will create a virtual environment named `.venv` with the correct Python version and install all the dependencies in the root directory.
80+
If you'd like a traditional virtual environment, you can run `uv sync --python=$(cat .python-version-default)` and it will create a virtual environment named `.venv` with the correct Python version and install all the dependencies in the root directory.
8181

8282
If you're using [*direnv*](https://direnv.net), you can automate the creation and activation of the project's virtual environment with the correct Python version by adding the following `.envrc` to the project root:
8383

@@ -220,7 +220,7 @@ $ uv run tox run -e docs-doctests
220220
Please note that the API docstrings are still reStructuredText.
221221

222222
- If you add or change public APIs, tag the docstring using `.. versionadded:: 24.1.0 WHAT` or `.. versionchanged:: 24.1.0 WHAT`.
223-
We follow CalVer, so the next version will be the current with with the middle number incremented (for example, `24.1.0` -> `24.2.0`).
223+
We follow CalVer, so the next version will be the current version with the middle number incremented (for example, `24.1.0` -> `24.2.0`).
224224

225225

226226
### Changelog

0 commit comments

Comments
 (0)