Skip to content

Commit f428814

Browse files
committed
fix: typos and minor documentation changes
Signed-off-by: David Calvert <[email protected]>
1 parent fa69eb7 commit f428814

File tree

3 files changed

+4
-3
lines changed

3 files changed

+4
-3
lines changed

CODE_OF_CONDUCT.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,8 @@ Community Impact Guidelines were inspired by
121121
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
122122

123123
For answers to common questions about this code of conduct, see the FAQ at
124-
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
124+
[https://www.contributor-covenant.org/faq][FAQ].\
125+
Translations are available at
125126
[https://www.contributor-covenant.org/translations][translations].
126127

127128
[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,6 @@ Changes are welcome as soon as they work with [kube-prometheus-stack](https://gi
1515

1616
## Best practices
1717

18+
- Bump dashboard(s) version(s)
1819
- [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) is preferred
1920
- [Signed commits](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff) is preferred
20-
- Bump dashboard(s) version(s)

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,7 @@ You will also need to enable and configure the Grafana `dashboards sidecar` like
198198

199199
### Broken panels due to a too high resolution
200200

201-
A user reported in [#50](https://github.com/dotdc/grafana-dashboards-kubernetes/issues/50) that some panels where broken because the default value of the `$resolution` variable was to low. The root cause hasn't been identified precisely, but he was using Grafana Agent & Grafana Mimir. Changing the `$resolution` variable to a higher value (a lower resolution) will likely solve the issue.
201+
A user reported in [#50](https://github.com/dotdc/grafana-dashboards-kubernetes/issues/50) that some panels were broken because the default value of the `$resolution` variable was too low. The root cause hasn't been identified precisely, but he was using Grafana Agent & Grafana Mimir. Changing the `$resolution` variable to a higher value (a lower resolution) will likely solve the issue.
202202
To make the fix permanent, you can configure the `Scrape interval` in your Grafana Datasource to a working value for your setup.
203203

204204
### Broken panels on k8s-views-nodes due to the nodename label

0 commit comments

Comments
 (0)