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

Fix spelling issues #151

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from
Open
Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ Then check the logs:
docker logs <problematic container, example: cdk-validium-sync>
```

Aditionaly, it can be worth checking the DBs:
Additionally, it can be worth checking the DBs:

- StateDB: `psql -h localhost -p 5432 -U state_user state_db`, password: `state_password`
- PoolDB: `psql -h localhost -p 5433 -U pool_user pool_db`, password: `pool_password`
Expand Down
2 changes: 1 addition & 1 deletion docs/ci/ok-to-test.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ don't require secrets and trusted actions are executed.
executed, and the from-fork actions are executed after a user with write access
comments in the PR `/ok-to-test sha=<commit sha>` with the sha of the commit over
which the actions should run. Before adding this comment the user should have
reviewed the code and verified that it won't suppose a security treat (for
reviewed the code and verified that it won't suppose a security threat (for
instance, the reviewer should verify that the PR is not adding new actions, or is
not trying to disclose the existing secrets).

Expand Down
2 changes: 1 addition & 1 deletion docs/ci/opsman.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Test operations package

We use the functionality provided by the [test operations package] in order to
manage components used during tests, specially e2e.
manage components used during tests, especially e2e.

The main functionality used currently in the tests is related to managing
containers, the package exposes the function `StartComponent` which takes a
Expand Down