reviewdog [vale] report
reported by reviewdog 🐶
Findings (23)
mission-control/docs/integrations/aws/cloudtrail.md|30 col 72| [Flanksource.Spelling] Is 'cloudtrail' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/aws/cloudformation.md|42 col 89| [Flanksource.Spelling] Is 'cloudformation' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/kubernetes/catalog.mdx|36 col 6| [Flanksource.Spelling] Is 'clusterName' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/kubernetes/catalog.mdx|47 col 161| [Flanksource.Spelling] Is 'automerge' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/kubernetes/catalog.mdx|48 col 47| [Flanksource.Spelling] Is 'trivy' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/kubernetes/catalog.mdx|49 col 215| [Flanksource.Spelling] Is 'PR's' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/crossplane.mdx|7 col 28| [Flanksource.Adverbs] Consider removing 'deeply'.
mission-control/docs/integrations/crossplane.mdx|15 col 29| [Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
mission-control/docs/integrations/crossplane.mdx|19 col 38| [Flanksource.Spelling] Is 'XRs' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/crossplane.mdx|27 col 24| [Flanksource.Spelling] Is 'XRs' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/crossplane.mdx|33 col 29| [Flanksource.Spelling] Is 'XRs' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/flux/playbooks.md|13 col 15| [Flanksource.Spelling] Is 'libary' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/flux/playbooks.md|15 col 34| [Flanksource.Spelling] Is 'hierachy' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/flux/playbooks.md|15 col 45| [Flanksource.Foreign] Use 'that is' instead of 'i.e.'.
mission-control/docs/integrations/flux/playbooks.md|44 col 5| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Just'.
mission-control/docs/integrations/flux/playbooks.md|46 col 1| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Just'.
mission-control/docs/integrations/flux/playbooks.md|46 col 34| [Flanksource.Spelling] Is 'mechnism' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/flux/playbooks.md|106 col 14| [Flanksource.Spelling] Is 'PR's' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/flux/playbooks.md|111 col 161| [Flanksource.Spelling] Is 'automerge' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/flux/playbooks.md|112 col 47| [Flanksource.Spelling] Is 'trivy' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/flux/playbooks.md|113 col 214| [Flanksource.Spelling] Is 'PR's' spelled correctly? Is it missing code formatting?
mission-control/docs/integrations/argo.mdx|17 col 89| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/integrations/terraform.mdx|20 col 85| [Flanksource.Spelling] Is 'ARNs' spelled correctly? Is it missing code formatting?
Filtered Findings (721)
docs/incidents/concepts/evidence.md|3 col 215| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
SECURITY.md|14 col 10| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
SECURITY.md|16 col 57| [Flanksource.Exclamation] Don't use exclamation points in text.
docs/incidents/concepts/done-definition.md|3 col 18| [Flanksource.Spelling] Is 'programatically' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/done-definition.md|13 col 73| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/incidents/concepts/done-definition.md|27 col 98| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/incidents/concepts/hypothesis.md|7 col 42| [Flanksource.Adverbs] Consider removing 'quickly'.
docs/apm-hub/concepts/templating.md|5 col 3| [alex.Condescending] Using 'Simply' may come across as condescending.
docs/apm-hub/concepts/templating.md|5 col 3| [Flanksource.Condescending] Using 'Simply' may come across as condescending.
docs/apm-hub/concepts/templating.md|5 col 3| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Simply'.
docs/apm-hub/concepts/templating.md|11 col 246| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/concepts/authentication.md|5 col 72| [Flanksource.Spelling] Is 'elasticsearch' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/file.md|1 col 18| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/file.md|36 col 39| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/api.md|5 col 8| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/concepts/api.md|15 col 137| [Vale.Repetition] 'include' is repeated!
docs/apm-hub/backends/opensearch.md|3 col 132| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/opensearch.md|55 col 42| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/opensearch.md|57 col 75| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/opensearch.md|57 col 99| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/opensearch.md|68 col 36| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/opensearch.md|69 col 36| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/opensearch.md|70 col 37| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/kubernetes.md|26 col 43| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/kubernetes.md|27 col 116| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|3 col 75| [Flanksource.Wordiness] Consider using 'all' instead of 'all of'.
docs/apm-hub/concepts/routing.md|16 col 104| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|20 col 131| [Flanksource.Spelling] Is 'idPrefix' spelled correctly? Is it missing code formatting?
docs/apm-hub/concepts/routing.md|31 col 206| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|42 col 53| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|46 col 14| [Flanksource.Adverbs] Consider removing 'really'.
docs/apm-hub/concepts/routing.md|57 col 5| [alex.Race] Consider using 'blocklisting', 'wronglisting', 'banlisting', or 'deny-listing' instead of 'Blacklisting'.
docs/apm-hub/concepts/routing.md|57 col 5| [Flanksource.RacialBias] Use 'denylisting' instead of 'Blacklisting'.
docs/apm-hub/concepts/routing.md|59 col 14| [alex.Race] Consider using 'blocklist', 'wronglist', 'banlist', or 'deny list' instead of 'blacklist'.
docs/apm-hub/concepts/routing.md|59 col 14| [Flanksource.RacialBias] Use 'denylist' instead of 'blacklist'.
docs/apm-hub/concepts/routing.md|85 col 240| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|85 col 384| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|85 col 410| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/quick-start.md|1 col 30| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'we'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/quick-start.md|15 col 89| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/quick-start.md|34 col 16| [Flanksource.Condescending] Using 'simple' may come across as condescending.
docs/apm-hub/quick-start.md|34 col 16| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simple'.
docs/apm-hub/quick-start.md|34 col 16| [alex.Condescending] Using 'simple' may come across as condescending.
docs/apm-hub/quick-start.md|40 col 11| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/elasticsearch.md|3 col 132| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/elasticsearch.md|55 col 42| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/elasticsearch.md|57 col 75| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/elasticsearch.md|57 col 99| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/elasticsearch.md|61 col 25| [Vale.Repetition] 'cloud' is repeated!
docs/apm-hub/backends/elasticsearch.md|62 col 17| [Flanksource.Spelling] Is 'APIKey' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/elasticsearch.md|72 col 36| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/elasticsearch.md|73 col 36| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/partials/_domain.mdx|3 col 76| [Flanksource.Spelling] Is 'minikube' spelled correctly? Is it missing code formatting?
canary-checker/docs/partials/_domain.mdx|3 col 95| [Flanksource.Spelling] Is 'routable' spelled correctly? Is it missing code formatting?
docs/apm-hub/overview.md|13 col 135| [Flanksource.Condescending] Using 'simply' may come across as condescending.
docs/apm-hub/overview.md|13 col 135| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simply'.
docs/apm-hub/overview.md|13 col 135| [alex.Condescending] Using 'simply' may come across as condescending.
docs/apm-hub/overview.md|26 col 5| [Flanksource.Spelling] Is 'fluentd' spelled correctly? Is it missing code formatting?
canary-checker/docs/partials/_gotemplate.md|29 col 68| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
CONTRIBUTING.md|9 col 78| [Flanksource.Spelling] Is 'humands' spelled correctly? Is it missing code formatting?
CONTRIBUTING.md|13 col 21| [Flanksource.Spelling] Is 'Submenu' spelled correctly? Is it missing code formatting?
CONTRIBUTING.md|27 col 87| [Flanksource.Spelling] Is 'html' spelled correctly? Is it missing code formatting?
CONTRIBUTING.md|28 col 92| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
CONTRIBUTING.md|34 col 87| [Flanksource.Adverbs] Consider removing 'really'.
canary-checker/tutorials/dev-guide.md|1 col 3| [Flanksource.Spelling] Is 'Dev' spelled correctly? Is it missing code formatting?
canary-checker/tutorials/dev-guide.md|9 col 15| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'we'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/dev-guide.md|22 col 68| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/dev-guide.md|24 col 12| [Flanksource.Spelling] Is 'nvm' spelled correctly? Is it missing code formatting?
canary-checker/tutorials/dev-guide.md|25 col 9| [Flanksource.Spelling] Is 'nvm' spelled correctly? Is it missing code formatting?
canary-checker/tutorials/dev-guide.md|33 col 25| [Flanksource.Spelling] Is 'distro' spelled correctly? Is it missing code formatting?
canary-checker/tutorials/dev-guide.md|37 col 19| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/dev-guide.md|39 col 74| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'they'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/dev-guide.md|70 col 18| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/prereqs.md|3 col 114| [Flanksource.Adverbs] Consider removing 'strictly'.
canary-checker/tutorials/prereqs.md|7 col 16| [Flanksource.Condescending] Using 'obvious' may come across as condescending.
canary-checker/tutorials/prereqs.md|7 col 16| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'obvious'.
canary-checker/tutorials/prereqs.md|7 col 16| [alex.Condescending] Using 'obvious' may come across as condescending.
canary-checker/tutorials/prereqs.md|7 col 223| [Flanksource.Adverbs] Consider removing 'properly'.
canary-checker/tutorials/prereqs.md|19 col 13| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/prereqs.md|52 col 281| [Flanksource.FirstPerson] Do not use the first person (such as ' I ').
canary-checker/tutorials/prereqs.md|85 col 1| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'You'll'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/concepts/push.mdx|5 col 70| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'just'.
canary-checker/README.md|27 col 76| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/README.md|62 col 11| [Flanksource.Spelling] Is 'Formating' spelled correctly? Is it missing code formatting?
canary-checker/README.md|122 col 27| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/README.md|140 col 3| [Flanksource.Spelling] Is 'canary_check_http_response_status' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/health-checks.md|5 col 197| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/concepts/health-checks.md|51 col 94| [Flanksource.Spelling] Is 'inlined' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|42 col 84| [Flanksource.Brevity] Avoid statements that don't add clarity, like 'It's important to note'.
mission-control/docs/topology/concepts/catalog.md|44 col 135| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'just'.
mission-control/docs/topology/concepts/templating.mdx|8 col 3| [Flanksource.Condescending] Using 'Simply' may come across as condescending.
mission-control/docs/topology/concepts/templating.mdx|8 col 3| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Simply'.
mission-control/docs/topology/concepts/templating.mdx|8 col 3| [alex.Condescending] Using 'Simply' may come across as condescending.
mission-control/docs/topology/concepts/templating.mdx|10 col 474| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'you'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|5 col 58| [Flanksource.Adverbs] Consider removing 'continually'.
canary-checker/tutorials/getting-started.md|7 col 16| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'you'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|17 col 24| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|17 col 42| [Flanksource.Adverbs] Consider removing 'quickly'.
canary-checker/tutorials/getting-started.md|17 col 54| [Flanksource.Condescending] Using 'simply' may come across as condescending.
canary-checker/tutorials/getting-started.md|17 col 54| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simply'.
canary-checker/tutorials/getting-started.md|17 col 54| [alex.Condescending] Using 'simply' may come across as condescending.
canary-checker/tutorials/getting-started.md|51 col 1| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'You'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|51 col 49| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|51 col 130| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'you'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|55 col 76| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|57 col 74| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|57 col 181| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|109 col 1| [Flanksource.Brevity] Avoid statements that don't add clarity, like 'You can see that'.
canary-checker/tutorials/getting-started.md|112 col 23| [alex.Condescending] Using 'simple' may come across as condescending.
canary-checker/tutorials/getting-started.md|112 col 23| [Flanksource.Condescending] Using 'simple' may come across as condescending.
canary-checker/tutorials/getting-started.md|112 col 23| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simple'.
canary-checker/tutorials/getting-started.md|140 col 80| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'you'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|184 col 51| [Flanksource.Condescending] Using 'simple' may come across as condescending.
canary-checker/tutorials/getting-started.md|184 col 51| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simple'.
canary-checker/tutorials/getting-started.md|184 col 51| [alex.Condescending] Using 'simple' may come across as condescending.
canary-checker/tutorials/getting-started.md|223 col 20| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'You'll'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/examples/prometheus.md|5 col 77| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/examples/flux.md|5 col 74| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/examples/flux.md|5 col 88| [Vale.Repetition] 'the' is repeated!
mission-control/docs/topology/examples/flux.md|9 col 5| [Flanksource.Spelling] Is 'Repos' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/index.md|14 col 1| [Flanksource.Wordiness] Consider using 'some' instead of 'Some of the'.
mission-control/docs/topology/index.md|25 col 25| [Flanksource.Spelling] Is 'SLO's' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/sql.mdx|59 col 40| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/lookups/exec.md|61 col 40| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/lookups/catalog.mdx|43 col 24| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/lookups/index.mdx|9 col 63| [Flanksource.Spelling] Is 'eg' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/index.mdx|16 col 27| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/lookups/http.mdx|34 col 15| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/topology/lookups/http.mdx|44 col 54| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|8 col 61| [Flanksource.Adverbs] Consider removing 'quickly'.
canary-checker/docs/scripting/cel.mdx|35 col 142| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|500 col 34| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|627 col 32| [Flanksource.Spelling] Is 'eturns' spelled correctly? Is it missing code formatting?
canary-checker/docs/scripting/cel.mdx|940 col 31| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|1614 col 66| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|1616 col 117| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|1618 col 12| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|1664 col 53| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|1701 col 41| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|1706 col 98| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/cel.mdx|1926 col 59| [Flanksource.Wordiness] Consider using 'to' instead of 'in order to'.
canary-checker/docs/scripting/cel.mdx|1950 col 50| [Flanksource.Adverbs] Consider removing 'safely'.
canary-checker/docs/scripting/cel.mdx|2300 col 68| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easy'.
canary-checker/docs/scripting/cel.mdx|2300 col 68| [alex.Condescending] Using 'easy' may come across as condescending.
canary-checker/docs/scripting/cel.mdx|2300 col 68| [Flanksource.Condescending] Using 'easy' may come across as condescending.
canary-checker/docs/scripting/cel.mdx|2351 col 63| [Flanksource.Condescending] Using 'easy' may come across as condescending.
canary-checker/docs/scripting/cel.mdx|2351 col 63| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easy'.
canary-checker/docs/scripting/cel.mdx|2351 col 63| [alex.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/partials/_domain.mdx|3 col 76| [Flanksource.Spelling] Is 'minikube' spelled correctly? Is it missing code formatting?
mission-control/docs/partials/_domain.mdx|3 col 95| [Flanksource.Spelling] Is 'routable' spelled correctly? Is it missing code formatting?
mission-control/docs/registry/kubernetes.md|94 col 75| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/partials/_gotemplate.md|29 col 68| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/playbooks/concepts/artifacts.md|58 col 28| [Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
mission-control/docs/playbooks/quick-start.mdx|8 col 9| [Flanksource.SpellingSuggestions] Use 'walk-through(s)' instead of 'walkthrough'.
mission-control/docs/playbooks/quick-start.mdx|8 col 22| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'we'll'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/playbooks/concepts/runners.md|5 col 184| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/playbooks/concepts/templating.mdx|55 col 55| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/playbooks/concepts/expression.md|7 col 157| [Flanksource.Adverbs] Consider removing 'nearly'.
mission-control/docs/playbooks/concepts/expression.md|45 col 8| [Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
mission-control/docs/playbooks/examples/restart-pod-on-check-failure.md|26 col 15| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/playbooks/examples/exec-delay.md|7 col 171| [Flanksource.Adverbs] Consider removing 'properly'.
mission-control/docs/playbooks/examples/exec-delay.md|34 col 60| [Flanksource.Adverbs] Consider removing 'properly'.
mission-control/docs/playbooks/examples/exec-delay.md|38 col 221| [Flanksource.Adverbs] Consider removing 'properly'.
mission-control/docs/playbooks/examples/exec-delay.md|65 col 60| [Flanksource.Adverbs] Consider removing 'properly'.
mission-control/docs/playbooks/index.mdx|20 col 29| [Flanksource.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/playbooks/index.mdx|20 col 29| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easy'.
mission-control/docs/playbooks/index.mdx|20 col 29| [alex.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/playbooks/index.mdx|46 col 5| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Just'.
canary-checker/docs/scripting/gotemplate.mdx|117 col 10| [Flanksource.SpellingSuggestions] Use 'data type(s)' instead of 'datatype'.
canary-checker/docs/scripting/gotemplate.mdx|139 col 10| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|152 col 12| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|214 col 185| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|214 col 190| [Flanksource.Condescending] Using 'simply' may come across as condescending.
canary-checker/docs/scripting/gotemplate.mdx|214 col 190| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simply'.
canary-checker/docs/scripting/gotemplate.mdx|214 col 190| [alex.Condescending] Using 'simply' may come across as condescending.
canary-checker/docs/scripting/gotemplate.mdx|300 col 6| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|300 col 76| [Flanksource.Foreign] Use 'that is' instead of 'i.e.'.
canary-checker/docs/scripting/gotemplate.mdx|510 col 11| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|545 col 68| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|545 col 97| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'Will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|563 col 67| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|618 col 47| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|685 col 10| [Flanksource.Condescending] Using 'obviously' may come across as condescending.
canary-checker/docs/scripting/gotemplate.mdx|685 col 10| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'obviously'.
canary-checker/docs/scripting/gotemplate.mdx|685 col 10| [alex.Condescending] Using 'obviously' may come across as condescending.
canary-checker/docs/scripting/gotemplate.mdx|814 col 68| [Flanksource.Spelling] Is 'diretory' spelled correctly? Is it missing code formatting?
canary-checker/docs/scripting/gotemplate.mdx|845 col 113| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|853 col 89| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|863 col 72| [Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
canary-checker/docs/scripting/gotemplate.mdx|879 col 83| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|889 col 72| [Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
canary-checker/docs/scripting/gotemplate.mdx|905 col 9| [Flanksource.Wordiness] Consider using 'whether' instead of 'whether or not'.
canary-checker/docs/scripting/gotemplate.mdx|907 col 62| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|922 col 9| [Flanksource.Wordiness] Consider using 'whether' instead of 'whether or not'.
canary-checker/docs/scripting/gotemplate.mdx|943 col 148| [Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
canary-checker/docs/scripting/gotemplate.mdx|951 col 149| [Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
canary-checker/docs/scripting/gotemplate.mdx|988 col 72| [Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
canary-checker/docs/scripting/gotemplate.mdx|1135 col 60| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|1157 col 81| [Flanksource.Foreign] Use 'that is' instead of 'i.e.'.
canary-checker/docs/scripting/gotemplate.mdx|1167 col 105| [Flanksource.Foreign] Use 'that is' instead of 'i.e.'.
canary-checker/docs/scripting/gotemplate.mdx|1196 col 110| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/scripting/gotemplate.mdx|1260 col 110| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
... (Too many findings. Dropped some findings)
Annotations
Check failure on line 30 in mission-control/docs/integrations/aws/cloudtrail.md
github-actions / vale
[vale] mission-control/docs/integrations/aws/cloudtrail.md#L30
[Flanksource.Spelling] Is 'cloudtrail' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'cloudtrail' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/aws/cloudtrail.md", "range": {"start": {"line": 30, "column": 72}}}, "severity": "ERROR"}
Check failure on line 42 in mission-control/docs/integrations/aws/cloudformation.md
github-actions / vale
[vale] mission-control/docs/integrations/aws/cloudformation.md#L42
[Flanksource.Spelling] Is 'cloudformation' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'cloudformation' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/aws/cloudformation.md", "range": {"start": {"line": 42, "column": 89}}}, "severity": "ERROR"}
Check failure on line 36 in mission-control/docs/integrations/kubernetes/catalog.mdx
github-actions / vale
[vale] mission-control/docs/integrations/kubernetes/catalog.mdx#L36
[Flanksource.Spelling] Is 'clusterName' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'clusterName' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/kubernetes/catalog.mdx", "range": {"start": {"line": 36, "column": 6}}}, "severity": "ERROR"}
Check failure on line 47 in mission-control/docs/integrations/kubernetes/catalog.mdx
github-actions / vale
[vale] mission-control/docs/integrations/kubernetes/catalog.mdx#L47
[Flanksource.Spelling] Is 'automerge' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'automerge' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/kubernetes/catalog.mdx", "range": {"start": {"line": 47, "column": 161}}}, "severity": "ERROR"}
Check failure on line 48 in mission-control/docs/integrations/kubernetes/catalog.mdx
github-actions / vale
[vale] mission-control/docs/integrations/kubernetes/catalog.mdx#L48
[Flanksource.Spelling] Is 'trivy' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'trivy' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/kubernetes/catalog.mdx", "range": {"start": {"line": 48, "column": 47}}}, "severity": "ERROR"}
Check failure on line 49 in mission-control/docs/integrations/kubernetes/catalog.mdx
github-actions / vale
[vale] mission-control/docs/integrations/kubernetes/catalog.mdx#L49
[Flanksource.Spelling] Is 'PR's' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'PR's' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/kubernetes/catalog.mdx", "range": {"start": {"line": 49, "column": 215}}}, "severity": "ERROR"}
Check warning on line 7 in mission-control/docs/integrations/crossplane.mdx
github-actions / vale
[vale] mission-control/docs/integrations/crossplane.mdx#L7
[Flanksource.Adverbs] Consider removing 'deeply'.
Raw output
{"message": "[Flanksource.Adverbs] Consider removing 'deeply'.", "location": {"path": "mission-control/docs/integrations/crossplane.mdx", "range": {"start": {"line": 7, "column": 28}}}, "severity": "WARNING"}
Check warning on line 15 in mission-control/docs/integrations/crossplane.mdx
github-actions / vale
[vale] mission-control/docs/integrations/crossplane.mdx#L15
[Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
Raw output
{"message": "[Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.", "location": {"path": "mission-control/docs/integrations/crossplane.mdx", "range": {"start": {"line": 15, "column": 29}}}, "severity": "WARNING"}
Check failure on line 19 in mission-control/docs/integrations/crossplane.mdx
github-actions / vale
[vale] mission-control/docs/integrations/crossplane.mdx#L19
[Flanksource.Spelling] Is 'XRs' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'XRs' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/crossplane.mdx", "range": {"start": {"line": 19, "column": 38}}}, "severity": "ERROR"}
Check failure on line 27 in mission-control/docs/integrations/crossplane.mdx
github-actions / vale
[vale] mission-control/docs/integrations/crossplane.mdx#L27
[Flanksource.Spelling] Is 'XRs' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'XRs' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/crossplane.mdx", "range": {"start": {"line": 27, "column": 24}}}, "severity": "ERROR"}
Check failure on line 33 in mission-control/docs/integrations/crossplane.mdx
github-actions / vale
[vale] mission-control/docs/integrations/crossplane.mdx#L33
[Flanksource.Spelling] Is 'XRs' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'XRs' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/crossplane.mdx", "range": {"start": {"line": 33, "column": 29}}}, "severity": "ERROR"}
Check failure on line 13 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L13
[Flanksource.Spelling] Is 'libary' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'libary' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 13, "column": 15}}}, "severity": "ERROR"}
Check failure on line 15 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L15
[Flanksource.Spelling] Is 'hierachy' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'hierachy' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 15, "column": 34}}}, "severity": "ERROR"}
Check failure on line 15 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L15
[Flanksource.Foreign] Use 'that is' instead of 'i.e.'.
Raw output
{"message": "[Flanksource.Foreign] Use 'that is' instead of 'i.e.'.", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 15, "column": 45}}}, "severity": "ERROR"}
Check failure on line 44 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L44
[Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Just'.
Raw output
{"message": "[Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Just'.", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 44, "column": 5}}}, "severity": "ERROR"}
Check failure on line 46 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L46
[Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Just'.
Raw output
{"message": "[Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Just'.", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 46, "column": 1}}}, "severity": "ERROR"}
Check failure on line 46 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L46
[Flanksource.Spelling] Is 'mechnism' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'mechnism' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 46, "column": 34}}}, "severity": "ERROR"}
Check failure on line 106 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L106
[Flanksource.Spelling] Is 'PR's' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'PR's' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 106, "column": 14}}}, "severity": "ERROR"}
Check failure on line 111 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L111
[Flanksource.Spelling] Is 'automerge' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'automerge' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 111, "column": 161}}}, "severity": "ERROR"}
Check failure on line 112 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L112
[Flanksource.Spelling] Is 'trivy' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'trivy' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 112, "column": 47}}}, "severity": "ERROR"}
Check failure on line 113 in mission-control/docs/integrations/flux/playbooks.md
github-actions / vale
[vale] mission-control/docs/integrations/flux/playbooks.md#L113
[Flanksource.Spelling] Is 'PR's' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'PR's' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/flux/playbooks.md", "range": {"start": {"line": 113, "column": 214}}}, "severity": "ERROR"}
Check warning on line 17 in mission-control/docs/integrations/argo.mdx
github-actions / vale
[vale] mission-control/docs/integrations/argo.mdx#L17
[Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
Raw output
{"message": "[Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.", "location": {"path": "mission-control/docs/integrations/argo.mdx", "range": {"start": {"line": 17, "column": 89}}}, "severity": "WARNING"}
Check failure on line 20 in mission-control/docs/integrations/terraform.mdx
github-actions / vale
[vale] mission-control/docs/integrations/terraform.mdx#L20
[Flanksource.Spelling] Is 'ARNs' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'ARNs' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/integrations/terraform.mdx", "range": {"start": {"line": 20, "column": 85}}}, "severity": "ERROR"}