fix spelling in markdown, use en_GB as lang

Signed-off-by: Sebastian Malton <sebastian@malton.name>
This commit is contained in:
Sebastian Malton committed 2020-12-01 15:38:01 -05:00
1 parent 111c518bf5
commit 7ebe700a3d
20 files changed
+169 -170

No files matched your search

+1 -1
View File
@@ -14,7 +14,7 @@ When contributing to this repository, please consider first discussing the chang
## Local Development Environment
> Prerequisites: Nodejs v12, make, yarn
> Prerequisites: NodeJS v12, make, yarn
* `make dev` - builds and starts the app
* `make clean` - cleanup local environment build artifacts
+2 -2
View File
@@ -18,7 +18,7 @@ When you create a new pull request, we expect some requirements to be met.
* When adding new documentation, add `New Documentation:` before the title. E.g. `New Documentation: Getting Started`
* When fixing documentation, add `Fix Documentation:` before the title. E.g. `Fix Documentation: Getting Started`
* When updating documentation, add `Update Documentation:` before the title. E.g. `Update Documentation: Getting Started`
* If your Pull Request closes an issue, you must write `Closes #ISSUE_NUMBER` where the ISSUE_NUMBER is the number in the end of the link url or the relevent issue. This will link your pull request to the issue, and when it is merged, the issue will close.
* If your Pull Request closes an issue, you must write `Closes #ISSUE_NUMBER` where the ISSUE_NUMBER is the number in the end of the link url or the relevant issue. This will link your pull request to the issue, and when it is merged, the issue will close.
* For each pull request made, we run tests to check if there are any broken links, the markdown formatting is valid, and the linter is passing.
@@ -28,6 +28,6 @@ Run a local instance of `mkdocs` in a docker container for developing the Lens D
> Prerequisites: docker, yarn
* `make docs` - local build and serve of mkdocs with auto update enabled
* `make docs` - local build and serve of `mkdocs` with auto update enabled
Go to [localhost:8000](http://127.0.0.1:8000).
+1 -1
View File
@@ -1,4 +1,4 @@
# Github Workflow
# GitHub Workflow
<!-- TOC -->
- [Fork The Project](#fork-the-project)
+1 -1
View File
@@ -6,7 +6,7 @@ The responsibilities of a community maintainer are listed below.
## Issues Triage
* **Labeling Issues:** Label issues accordingly.
* **Labelling Issues:** Label issues accordingly.
* **Finding Duplicates:** Finding and closing duplicate issues.
* **Doing First Level Contact:** Getting more information on the issues (like version number or asking for clarification) if needed.
* **Closing Irrelevant Issues:** Closing issues that are determined irrelevant, no longer needed, not relevant to the project and/or don't follow the issues guidelines.
+2 -2
View File
@@ -2,9 +2,9 @@
Help promote Lens! If you are not a developer (or even if you are), you can still contribute to the project – a lot – by helping us to promote it. As we are a free and open source project, the community is our most important asset. Here are some ways that you can help the project continue to grow.
## Follow, Like, Recommend, Favorite, Vote and Star Us
## Follow, Like, Recommend, Favourite, Vote and Star Us
There are many sites where you can vote, recommend, favorite, and star us.
There are many sites where you can vote, recommend, favourite, and star us.
* [Twitter](https://twitter.com/k8slens) - Like, comment and retweet our posts, and follow us on Twitter.
* [Medium](https://medium.com/k8slens) - Give claps to our articles and follow us on Medium.
+2 -2
View File
@@ -1,6 +1,6 @@
## Testing Your Code
Lens uses github actions to run automated tests on any PR, before merging.
Lens uses Github actions to run automated tests on any PR, before merging.
However, a PR will not be reviewed before all tests are green, so to save time and prevent your PR from going stale, it is best to test it before submitting the PR.
### Run Local Verifications
@@ -22,7 +22,7 @@ In the repository root directory, make sure that:
* `make build` runs successfully.
* `make test` runs successfully.
* `make integration` runs successfully (some tests require minikube running).
* `make integration` runs successfully (some tests require `minikube` running).
Please note that this last test is prone to "flakiness", so it might fail on occasion. If it fails constantly, take a deeper look at your code to find the source of the problem.