Skip to content

Commit 53fa575

Browse files
authored
Merge pull request #1656 from mathbunnyru/asalikhov/pycharm_issues
Fix English typos and misc details detected by PyCharm
2 parents 25add57 + 6bd5919 commit 53fa575

File tree

20 files changed

+58
-47
lines changed

20 files changed

+58
-47
lines changed

.gitignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -162,3 +162,6 @@ cython_debug/
162162

163163
# VS Code project configuration
164164
.vscode/
165+
166+
# PyCharm project configuration
167+
.idea/

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Jupyter Docker Stacks
22

3-
[![Github actions badge](https://github.com/jupyter/docker-stacks/actions/workflows/docker.yml/badge.svg)](https://github.com/jupyter/docker-stacks/actions/workflows/docker.yml "Docker images build status")
3+
[![GitHub actions badge](https://github.com/jupyter/docker-stacks/actions/workflows/docker.yml/badge.svg)](https://github.com/jupyter/docker-stacks/actions/workflows/docker.yml "Docker images build status")
44
[![Read the Docs badge](https://img.shields.io/readthedocs/jupyter-docker-stacks.svg)](https://jupyter-docker-stacks.readthedocs.io/en/latest/ "Documentation build status")
55
[![pre-commit.ci status](https://results.pre-commit.ci/badge/github/jupyter/docker-stacks/master.svg)](https://results.pre-commit.ci/latest/github/jupyter/docker-stacks/master "pre-commit.ci build status")
66
[![Discourse badge](https://img.shields.io/discourse/users.svg?color=%23f37626&server=https%3A%2F%2Fdiscourse.jupyter.org)](https://discourse.jupyter.org/ "Jupyter Discourse Forum")

docs/conf.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,6 @@
9797

9898
linkcheck_allowed_redirects = {
9999
r"https://results\.pre-commit\.ci/latest/github/jupyter/docker-stacks/master": r"https://results\.pre-commit\.ci/run/github/.*", # Latest master CI build
100-
r"https://github\.com/jupyter/docker-stacks/issues/new.*": r"https://github\.com/login.*", # Github wants user to be logon to use this features
100+
r"https://github\.com/jupyter/docker-stacks/issues/new.*": r"https://github\.com/login.*", # GitHub wants user to be logon to use this features
101101
r"https://github\.com/orgs/jupyter/teams/docker-image-maintainers/members": r"https://github\.com/login.*",
102102
}

docs/contributing/issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Please review the following guidelines when reporting your problem.
1010
please search the [jupyter/docker-stacks issue tracker](https://github.com/jupyter/docker-stacks/issues)
1111
to see if someone else has already reported the same problem.
1212
If not, please open a [GitHub bug report issue](https://github.com/jupyter/docker-stacks/issues/new?assignees=&labels=type%3ABug&template=bug_report.md&title=)
13-
and provide all of the information requested in the issue template.
13+
and provide all the information requested in the issue template.
1414
Additionally, make sure to check the [Troubleshooting common error](../using/troubleshooting.md) page in the documentation before submitting an issue.
1515
- If the issue you're seeing is with one of the open-source libraries included in the Docker images and is reproducible outside the images,
1616
please file a bug with the appropriate open source project.

docs/contributing/lint.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ make pre-commit-install
2727
### Run
2828

2929
Now pre-commit (and so configured hooks) will run automatically on `git commit` on each changed file.
30-
However it is also possible to trigger it against all files.
30+
However, it is also possible to trigger it against all files.
3131

3232
```{note}
3333
Hadolint pre-commit uses docker to run, so docker should be running while running this command.

docs/contributing/packages.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ We pin major.minor version of python, so this will stay the same even after invo
1111

1212
## Outdated packages
1313

14-
In order to help identifying packages that can be updated you can use the following helper tool.
14+
In order to help to identify packages that can be updated you can use the following helper tool.
1515
It will list all the packages installed in the `Dockerfile` that can be updated -- dependencies are
1616
filtered to focus only on requested packages.
1717

docs/contributing/stacks.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ and the documentation below to help you get started defining, building, and shar
66

77
Following these steps will:
88

9-
1. Setup a project on GitHub containing a Dockerfile based on any of the images we provide.
9+
1. Set up a project on GitHub containing a Dockerfile based on any of the images we provide.
1010
2. Configure GitHub Actions to build and test your image when users submit pull requests to your repository.
1111
3. Configure Docker Hub to build and host your images for others to use.
1212
4. Update the [list of community stacks](../using/selecting.md#community-stacks) in this documentation to include your image.
@@ -70,7 +70,7 @@ git push -u origin main
7070

7171
The cookiecutter template comes with a `.github/workflows/docker.yml` file, which allows you to use GitHub actions to build your Docker image whenever you or someone else submits a pull request.
7272

73-
1. By default the `.github/workflows/docker.yaml` file has the following triggers configuration:
73+
1. By default, the `.github/workflows/docker.yaml` file has the following triggers configuration:
7474

7575
```yaml
7676
on:
@@ -112,7 +112,7 @@ you merge a GitHub pull request to the master branch of your project.
112112
7. Select the GitHub organization and repository containing your image definition from the dropdowns.
113113
![Dockerhub - Create Repository page focusing on the "Select Repository" dropdown menu](../_static/docker-github-settings.png)
114114
8. Click the **Create and Build** button.
115-
9. Click on your avatar on the top-right corner and select Account settings.
115+
9. Click on your avatar in the top-right corner and select Account settings.
116116
![DockerHub page zoomed into the user's settings and accounts menu](../_static/docker-org-select.png)
117117
10. Click on **Security** and then click on the **New Access Token** button.
118118
![DockerHub - Account page with the "Security" tab active and a rectangle highlighting the "New Access Token" button in the UI](../_static/docker-org-security.png)
@@ -126,7 +126,7 @@ you merge a GitHub pull request to the master branch of your project.
126126

127127
13. Head back to your GitHub repository and click on the **Settings tab**.
128128
![GitHub page with the the "Setting" tab active and a rectangle highlighting the "New repository secret" button in the UI](../_static/github-create-secrets.png)
129-
14. Click on the **Secrets** section and then on the **New repository secret** button on the top right corner (see image above).
129+
14. Click on the **Secrets** section and then on the **New repository secret** button in the top right corner (see image above).
130130
15. Create a **DOCKERHUB_TOKEN** secret and paste the Personal Access Token from DockerHub in the **value** field.
131131
![GitHub - Actions/New secret page with the Name field set to "DOCKERHUB_TOKEN"](../_static/github-secret-token.png)
132132
16. Repeat the above step but creating a **DOCKERHUB_USERNAME** and replacing the _value_ field with your DockerHub username.

docs/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,6 @@ Table of Contents
3737
:maxdepth: 2
3838
:caption: Getting Help
3939

40-
Issue Tracker on Github <https://github.com/jupyter/docker-stacks/issues>
40+
Issue Tracker on GitHub <https://github.com/jupyter/docker-stacks/issues>
4141
Jupyter Discourse Forum <https://discourse.jupyter.org>
4242
Jupyter Website <https://jupyter.org>

docs/maintaining/tasks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ When there's a new stack definition, do the following before merging the PR with
5151

5252
## Pushing a Build Manually
5353

54-
If automated build in Github Actions has got you down, do the following to push a build manually:
54+
If automated build in GitHub Actions has got you down, do the following to push a build manually:
5555

5656
1. Clone this repository.
5757
2. Check out the git SHA you want to build and publish.

docs/using/common.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ You can further customize the container environment by adding shell scripts (`*.
129129
or executables (`chmod +x`) to be run to the paths below:
130130

131131
- `/usr/local/bin/start-notebook.d/` - handled **before** any of the standard options noted above are applied
132-
- `/usr/local/bin/before-notebook.d/` - handled **after** all of the standard options noted above are applied
132+
- `/usr/local/bin/before-notebook.d/` - handled **after** all the standard options noted above are applied
133133
and ran right before the notebook server launches
134134

135135
See the `run-hooks` function in the [`jupyter/base-notebook start.sh`](https://github.com/jupyter/docker-stacks/blob/master/base-notebook/start.sh)
@@ -216,7 +216,7 @@ docker run -it --rm \
216216
### `start.sh`
217217

218218
The `start-notebook.sh` script inherits most of its option handling capability from a more generic `start.sh` script.
219-
The `start.sh` script supports all of the features described above but allows you to specify an arbitrary command to execute.
219+
The `start.sh` script supports all the features described above but allows you to specify an arbitrary command to execute.
220220
For example, to run the text-based `ipython` console in a container, do the following:
221221

222222
```bash

0 commit comments

Comments
 (0)