chore: don't use Prettier for mdx #132
reviewdog [vale] report
reported by reviewdog 🐶
Findings (4727)
mission-control/docs/hardening.md|36 col 73| [Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/hardening.md|36 col 73| [Vale.Spelling] Did you really mean 'namespace'?
mission-control/docs/hardening.md|39 col 103| [alex.Ablist] When referring to a person, consider using 'turned off', 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'disabled'.
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/health-checks.md|51 col 94| [Vale.Spelling] Did you really mean 'inlined'?
mission-control/docs/topology/concepts/properties.mdx|59 col 42| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/properties.mdx|59 col 42| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
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/prometheus.md|5 col 95| [Flanksource.Spelling] Is 'kubernetes' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/examples/prometheus.md|5 col 95| [Vale.Spelling] Did you really mean 'kubernetes'?
mission-control/docs/topology/examples/prometheus.md|5 col 131| [Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/examples/prometheus.md|5 col 131| [Vale.Spelling] Did you really mean 'namespace'?
mission-control/docs/topology/concepts/catalog.md|5 col 30| [Vale.Spelling] Did you really mean 'configs'?
mission-control/docs/topology/concepts/catalog.md|5 col 30| [Flanksource.Spelling] Is 'configs' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|5 col 50| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|5 col 50| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|7 col 59| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|7 col 59| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|9 col 13| [Vale.Spelling] Did you really mean 'Config'?
mission-control/docs/topology/concepts/catalog.md|9 col 13| [Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|30 col 4| [Vale.Spelling] Did you really mean 'Config'?
mission-control/docs/topology/concepts/catalog.md|30 col 4| [Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|34 col 43| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|34 col 43| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|35 col 43| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|35 col 43| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|36 col 31| [Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|36 col 31| [Vale.Spelling] Did you really mean 'namespace'?
mission-control/docs/topology/concepts/catalog.md|36 col 48| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|36 col 48| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|37 col 35| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|37 col 35| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|38 col 35| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|38 col 35| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|39 col 35| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|39 col 35| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|40 col 35| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|40 col 35| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|42 col 38| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|42 col 38| [Flanksource.Spelling] Is 'config' 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|42 col 134| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|42 col 134| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/catalog.md|44 col 105| [Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|44 col 105| [Vale.Spelling] Did you really mean 'namespace'?
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/catalog.md|44 col 154| [Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/catalog.md|44 col 154| [Vale.Spelling] Did you really mean 'namespace'?
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|24 col 5| [Vale.Spelling] Did you really mean 'Config'?
mission-control/docs/topology/index.md|24 col 5| [Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
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/index.md|25 col 25| [Vale.Spelling] Did you really mean 'SLO's'?
mission-control/docs/topology/index.md|50 col 18| [Vale.Spelling] Did you really mean 'Config'?
mission-control/docs/topology/index.md|50 col 18| [Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/index.md|52 col 56| [Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/index.md|52 col 56| [Vale.Spelling] Did you really mean 'Config'?
mission-control/docs/topology/index.md|52 col 94| [Flanksource.Spelling] Is 'Namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/index.md|52 col 94| [Vale.Spelling] Did you really mean 'Namespace'?
mission-control/docs/topology/index.md|52 col 144| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/index.md|52 col 144| [Vale.Spelling] Did you really mean 'config'?
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|7 col 70| [Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/examples/flux.md|7 col 70| [Vale.Spelling] Did you really mean 'namespace'?
mission-control/docs/topology/examples/flux.md|8 col 43| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/examples/flux.md|8 col 43| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/examples/flux.md|9 col 5| [Vale.Spelling] Did you really mean 'Repos'?
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/examples/flux.md|9 col 43| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/examples/flux.md|9 col 43| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/examples/flux.md|10 col 5| [Vale.Spelling] Did you really mean 'Kustomizations'?
mission-control/docs/topology/examples/flux.md|10 col 5| [Flanksource.Spelling] Is 'Kustomizations' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/examples/flux.md|10 col 36| [Vale.Spelling] Did you really mean 'Kustomization'?
mission-control/docs/topology/examples/flux.md|10 col 36| [Flanksource.Spelling] Is 'Kustomization' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/examples/flux.md|10 col 50| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/examples/flux.md|10 col 50| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/examples/flux.md|11 col 40| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/examples/flux.md|11 col 40| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/lookups/catalog.mdx|9 col 48| [Vale.Spelling] Did you really mean 'configs'?
mission-control/docs/topology/lookups/catalog.mdx|9 col 48| [Flanksource.Spelling] Is 'configs' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/catalog.mdx|38 col 48| [alex.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
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/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 171| [Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|10 col 171| [Vale.Spelling] Did you really mean 'Config'?
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'.
mission-control/docs/topology/concepts/templating.mdx|18 col 4| [Vale.Spelling] Did you really mean 'Javascript'?
mission-control/docs/topology/concepts/templating.mdx|18 col 4| [Flanksource.Spelling] Is 'Javascript' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|23 col 41| [Flanksource.Spelling] Is 'Expr' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|23 col 41| [Vale.Spelling] Did you really mean 'Expr'?
mission-control/docs/topology/concepts/templating.mdx|54 col 5| [Flanksource.Spelling] Is 'Javascript' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|54 col 5| [Vale.Spelling] Did you really mean 'Javascript'?
mission-control/docs/topology/concepts/templating.mdx|56 col 9| [Vale.Spelling] Did you really mean 'javascript'?
mission-control/docs/topology/concepts/templating.mdx|56 col 9| [Flanksource.Spelling] Is 'javascript' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|56 col 65| [Flanksource.Spelling] Is 'Javascript' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|56 col 65| [Vale.Spelling] Did you really mean 'Javascript'?
mission-control/docs/topology/concepts/templating.mdx|57 col 32| [Flanksource.Spelling] Is 'Javascript' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|57 col 32| [Vale.Spelling] Did you really mean 'Javascript'?
mission-control/docs/topology/concepts/templating.mdx|71 col 5| [Flanksource.Spelling] Is 'javascript' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|71 col 5| [Vale.Spelling] Did you really mean 'javascript'?
mission-control/docs/topology/concepts/templating.mdx|73 col 5| [Vale.Spelling] Did you really mean 'JSONPath'?
mission-control/docs/topology/concepts/templating.mdx|75 col 3| [Vale.Spelling] Did you really mean 'JSONPath'?
mission-control/docs/topology/concepts/templating.mdx|75 col 38| [Flanksource.Spelling] Is 'XPath' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|75 col 38| [Vale.Spelling] Did you really mean 'XPath'?
mission-control/docs/topology/concepts/templating.mdx|75 col 204| [Vale.Spelling] Did you really mean 'Config'?
mission-control/docs/topology/concepts/templating.mdx|75 col 204| [Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|76 col 28| [Vale.Spelling] Did you really mean 'JSONPath'?
mission-control/docs/topology/concepts/templating.mdx|76 col 101| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|76 col 101| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/topology/concepts/templating.mdx|76 col 117| [Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/concepts/templating.mdx|76 col 117| [Vale.Spelling] Did you really mean 'Config'?
mission-control/docs/topology/concepts/templating.mdx|87 col 40| [Vale.Spelling] Did you really mean 'JSONPath'?
mission-control/docs/topology/lookups/exec.md|10 col 3| [Vale.Spelling] Did you really mean 'Powershell'?
mission-control/docs/topology/lookups/exec.md|10 col 3| [Flanksource.Spelling] Is 'Powershell' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/exec.md|54 col 87| [alex.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
mission-control/docs/topology/lookups/exec.md|54 col 108| [alex.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
mission-control/docs/topology/lookups/exec.md|54 col 121| [Flanksource.Spelling] Is 'powershell' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/exec.md|54 col 121| [Vale.Spelling] Did you really mean 'powershell'?
mission-control/docs/topology/lookups/exec.md|54 col 139| [Vale.Spelling] Did you really mean 'darwin'?
mission-control/docs/topology/lookups/exec.md|54 col 139| [Flanksource.Spelling] Is 'darwin' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/exec.md|54 col 156| [alex.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
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/exec.md|65 col 16| [Flanksource.Spelling] Is 'stdout' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/exec.md|65 col 16| [Vale.Spelling] Did you really mean 'stdout'?
mission-control/docs/topology/lookups/exec.md|66 col 16| [Flanksource.Spelling] Is 'stderr' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/exec.md|66 col 16| [Vale.Spelling] Did you really mean 'stderr'?
mission-control/docs/topology/lookups/prometheus.md|43 col 53| [Vale.Spelling] Did you really mean 'prometheus'?
mission-control/docs/topology/lookups/prometheus.md|43 col 53| [Flanksource.Spelling] Is 'prometheus' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/prometheus.md|47 col 23| [Flanksource.Spelling] Is 'prometheus' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/prometheus.md|47 col 23| [Vale.Spelling] Did you really mean 'prometheus'?
mission-control/docs/topology/lookups/sql.mdx|9 col 5| [Flanksource.Spelling] Is 'postgres' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/sql.mdx|9 col 5| [Vale.Spelling] Did you really mean 'postgres'?
mission-control/docs/topology/lookups/sql.mdx|9 col 83| [Flanksource.Spelling] Is 'Postgres' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/sql.mdx|9 col 83| [Vale.Spelling] Did you really mean 'Postgres'?
mission-control/docs/topology/lookups/sql.mdx|55 col 45| [alex.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
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/sql.mdx|63 col 13| [Vale.Spelling] Did you really mean 'stderr'?
mission-control/docs/topology/lookups/sql.mdx|63 col 13| [Flanksource.Spelling] Is 'stderr' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/sql.mdx|98 col 29| [Vale.Spelling] Did you really mean 'Postgres'?
mission-control/docs/topology/lookups/sql.mdx|98 col 29| [Flanksource.Spelling] Is 'Postgres' spelled correctly? Is it missing code formatting?
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|39 col 33| [Vale.Spelling] Did you really mean 'url'?
mission-control/docs/topology/lookups/http.mdx|44 col 12| [Vale.Spelling] Did you really mean 'templateBody'?
mission-control/docs/topology/lookups/http.mdx|44 col 12| [Flanksource.Spelling] Is 'templateBody' spelled correctly? Is it missing code formatting?
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'.
mission-control/docs/topology/lookups/http.mdx|44 col 62| [Vale.Spelling] Did you really mean 'templated'?
mission-control/docs/topology/lookups/http.mdx|44 col 62| [Flanksource.Spelling] Is 'templated' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/mongo.md|7 col 80| [Flanksource.Spelling] Is 'Postgres' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/mongo.md|7 col 80| [Vale.Spelling] Did you really mean 'Postgres'?
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 76| [Vale.Spelling] Did you really mean 'minikube'?
mission-control/docs/partials/_domain.mdx|3 col 95| [Flanksource.Spelling] Is 'routable' spelled correctly? Is it missing code formatting?
mission-control/docs/partials/_domain.mdx|3 col 95| [Vale.Spelling] Did you really mean 'routable'?
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|9 col 63| [Vale.Spelling] Did you really mean 'eg'?
mission-control/docs/topology/lookups/index.mdx|9 col 85| [Vale.Spelling] Did you really mean 'kubernetes'?
mission-control/docs/topology/lookups/index.mdx|9 col 85| [Flanksource.Spelling] Is 'kubernetes' 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/index.mdx|16 col 94| [Flanksource.Spelling] Is 'kubernetes' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/index.mdx|16 col 94| [Vale.Spelling] Did you really mean 'kubernetes'?
mission-control/docs/topology/lookups/index.mdx|49 col 5| [Vale.Spelling] Did you really mean 'forEach'?
mission-control/docs/topology/lookups/index.mdx|49 col 5| [Flanksource.Spelling] Is 'forEach' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/index.mdx|51 col 36| [Vale.Spelling] Did you really mean 'kubernetes'?
mission-control/docs/topology/lookups/index.mdx|51 col 36| [Flanksource.Spelling] Is 'kubernetes' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/index.mdx|95 col 19| [Flanksource.Spelling] Is 'forEach' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/index.mdx|95 col 19| [Vale.Spelling] Did you really mean 'forEach'?
mission-control/docs/topology/lookups/index.mdx|95 col 31| [Flanksource.Spelling] Is 'templatable' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/index.mdx|95 col 31| [Vale.Spelling] Did you really mean 'templatable'?
mission-control/docs/topology/lookups/kubernetes.md|7 col 41| [Vale.Spelling] Did you really mean 'kubernetes'?
mission-control/docs/topology/lookups/kubernetes.md|7 col 41| [Flanksource.Spelling] Is 'kubernetes' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/kubernetes.md|42 col 3| [Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/kubernetes.md|42 col 3| [Vale.Spelling] Did you really mean 'namespace'?
mission-control/docs/topology/lookups/kubernetes.md|42 col 25| [Vale.Spelling] Did you really mean 'namespace'?
mission-control/docs/topology/lookups/kubernetes.md|42 col 25| [Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/kubernetes.md|43 col 102| [Vale.Spelling] Did you really mean 'bool'?
mission-control/docs/topology/lookups/kubernetes.md|52 col 3| [Flanksource.Spelling] Is 'labelSelector' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/kubernetes.md|52 col 3| [Vale.Spelling] Did you really mean 'labelSelector'?
mission-control/docs/topology/lookups/kubernetes.md|53 col 3| [Flanksource.Spelling] Is 'fieldSelector' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/kubernetes.md|53 col 3| [Vale.Spelling] Did you really mean 'fieldSelector'?
mission-control/docs/topology/lookups/kubernetes.md|57 col 68| [Flanksource.Spelling] Is 'kubernetes' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/kubernetes.md|57 col 68| [Vale.Spelling] Did you really mean 'kubernetes'?
mission-control/docs/reference/scripting/javascript.md|5 col 82| [Flanksource.Spelling] Is 'Javascript' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/javascript.md|5 col 82| [Vale.Spelling] Did you really mean 'Javascript'?
mission-control/docs/reference/scripting/javascript.md|30 col 99| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/topology/_forEach.md|5 col 33| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/reference/topology/_forEach.md|5 col 33| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/_lookup.md|5 col 25| [Flanksource.Spelling] Is 'kubernetes' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/_lookup.md|5 col 25| [Vale.Spelling] Did you really mean 'kubernetes'?
mission-control/docs/reference/scripting/_functions.md|1 col 43| [Flanksource.Spelling] Is 'gomplate' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/_functions.md|1 col 43| [Vale.Spelling] Did you really mean 'gomplate'?
mission-control/docs/reference/scripting/_functions.md|7 col 365| [Flanksource.Spelling] Is 'lt' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/_functions.md|7 col 365| [Vale.Spelling] Did you really mean 'lt'?
mission-control/docs/reference/scripting/_functions.md|7 col 373| [Flanksource.Spelling] Is 'le' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/_functions.md|7 col 373| [Vale.Spelling] Did you really mean 'le'?
mission-control/docs/reference/scripting/_functions.md|48 col 4| [Flanksource.Spelling] Is 'json' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/_functions.md|48 col 4| [Vale.Spelling] Did you really mean 'json'?
mission-control/docs/reference/scripting/_functions.md|49 col 4| [Vale.Spelling] Did you really mean 'jsonArray'?
mission-control/docs/reference/scripting/_functions.md|49 col 4| [Flanksource.Spelling] Is 'jsonArray' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/_functions.md|50 col 4| [Vale.Spelling] Did you really mean 'yaml'?
mission-control/docs/reference/scripting/_functions.md|51 col 4| [Flanksource.Spelling] Is 'yamlArray' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/_functions.md|51 col 4| [Vale.Spelling] Did you really mean 'yamlArray'?
mission-control/docs/reference/scripting/_functions.md|52 col 4| [Vale.Spelling] Did you really mean 'toml'?
mission-control/docs/reference/scripting/_functions.md|53 col 4| [Vale.Spelling] Did you really mean 'csv'?
mission-control/docs/reference/scripting/_functions.md|57 col 4| [Vale.Spelling] Did you really mean 'toJSONPretty'?
mission-control/docs/reference/scripting/_functions.md|57 col 4| [Flanksource.Spelling] Is 'toJSONPretty' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/_functions.md|65 col 192| [Vale.Spelling] Did you really mean 'tim'?
mission-control/docs/reference/scripting/_functions.md|65 col 192| [Flanksource.Spelling] Is 'tim' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|11 col 74| [Flanksource.Spelling] Is 'millicores' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|11 col 74| [Vale.Spelling] Did you really mean 'millicores'?
mission-control/docs/reference/topology/properties.md|12 col 24| [alex.ProfanityUnlikely] Be careful with 'color', it's profane in some cases.
mission-control/docs/reference/topology/properties.md|16 col 30| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/topology/properties.md|21 col 24| [Vale.Spelling] Did you really mean 'tooltip'?
mission-control/docs/reference/topology/properties.md|21 col 24| [Flanksource.Spelling] Is 'tooltip' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|21 col 54| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/topology/properties.md|22 col 49| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|22 col 49| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/reference/topology/properties.md|29 col 19| [Vale.Spelling] Did you really mean 'url'?
mission-control/docs/reference/topology/properties.md|30 col 19| [Flanksource.Spelling] Is 'tooltip' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|30 col 19| [Vale.Spelling] Did you really mean 'tooltip'?
mission-control/docs/reference/topology/properties.md|35 col 4| [Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|35 col 4| [Vale.Spelling] Did you really mean 'Config'?
mission-control/docs/reference/topology/properties.md|39 col 37| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|39 col 37| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/reference/topology/properties.md|40 col 33| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/reference/topology/properties.md|40 col 33| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|41 col 41| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/reference/topology/properties.md|41 col 41| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|42 col 23| [Vale.Spelling] Did you really mean 'JSONPath'?
mission-control/docs/reference/topology/properties.md|42 col 70| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|42 col 70| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/reference/topology/properties.md|44 col 33| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/reference/topology/properties.md|44 col 33| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|44 col 46| [Flanksource.Adverbs] Consider removing 'rarely'.
mission-control/docs/reference/topology/index.mdx|12 col 40| [Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/index.mdx|12 col 40| [Vale.Spelling] Did you really mean 'config'?
mission-control/docs/reference/topology/index.mdx|18 col 52| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/topology/index.mdx|19 col 22| [Flanksource.Spelling] Is 'tooltip' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/index.mdx|19 col 22| [Vale.Spelling] Did you really mean 'tooltip'?
... (Too many findings. Dropped some findings)
Annotations
Check failure on line 36 in mission-control/docs/hardening.md
github-actions / vale
[vale] mission-control/docs/hardening.md#L36
[Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/hardening.md", "range": {"start": {"line": 36, "column": 73}}}, "severity": "ERROR"}
Check failure on line 36 in mission-control/docs/hardening.md
github-actions / vale
[vale] mission-control/docs/hardening.md#L36
[Vale.Spelling] Did you really mean 'namespace'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'namespace'?", "location": {"path": "mission-control/docs/hardening.md", "range": {"start": {"line": 36, "column": 73}}}, "severity": "ERROR"}
Check warning on line 39 in mission-control/docs/hardening.md
github-actions / vale
[vale] mission-control/docs/hardening.md#L39
[alex.Ablist] When referring to a person, consider using 'turned off', 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'disabled'.
Raw output
{"message": "[alex.Ablist] When referring to a person, consider using 'turned off', 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'disabled'.", "location": {"path": "mission-control/docs/hardening.md", "range": {"start": {"line": 39, "column": 103}}}, "severity": "WARNING"}
Check warning on line 5 in mission-control/docs/topology/concepts/health-checks.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/health-checks.md#L5
[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/topology/concepts/health-checks.md", "range": {"start": {"line": 5, "column": 197}}}, "severity": "WARNING"}
Check failure on line 51 in mission-control/docs/topology/concepts/health-checks.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/health-checks.md#L51
[Flanksource.Spelling] Is 'inlined' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'inlined' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/concepts/health-checks.md", "range": {"start": {"line": 51, "column": 94}}}, "severity": "ERROR"}
Check failure on line 51 in mission-control/docs/topology/concepts/health-checks.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/health-checks.md#L51
[Vale.Spelling] Did you really mean 'inlined'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'inlined'?", "location": {"path": "mission-control/docs/topology/concepts/health-checks.md", "range": {"start": {"line": 51, "column": 94}}}, "severity": "ERROR"}
Check failure on line 59 in mission-control/docs/topology/concepts/properties.mdx
github-actions / vale
[vale] mission-control/docs/topology/concepts/properties.mdx#L59
[Vale.Spelling] Did you really mean 'config'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'config'?", "location": {"path": "mission-control/docs/topology/concepts/properties.mdx", "range": {"start": {"line": 59, "column": 42}}}, "severity": "ERROR"}
Check failure on line 59 in mission-control/docs/topology/concepts/properties.mdx
github-actions / vale
[vale] mission-control/docs/topology/concepts/properties.mdx#L59
[Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/concepts/properties.mdx", "range": {"start": {"line": 59, "column": 42}}}, "severity": "ERROR"}
Check warning on line 5 in mission-control/docs/topology/examples/prometheus.md
github-actions / vale
[vale] mission-control/docs/topology/examples/prometheus.md#L5
[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/topology/examples/prometheus.md", "range": {"start": {"line": 5, "column": 77}}}, "severity": "WARNING"}
Check failure on line 5 in mission-control/docs/topology/examples/prometheus.md
github-actions / vale
[vale] mission-control/docs/topology/examples/prometheus.md#L5
[Flanksource.Spelling] Is 'kubernetes' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'kubernetes' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/examples/prometheus.md", "range": {"start": {"line": 5, "column": 95}}}, "severity": "ERROR"}
Check failure on line 5 in mission-control/docs/topology/examples/prometheus.md
github-actions / vale
[vale] mission-control/docs/topology/examples/prometheus.md#L5
[Vale.Spelling] Did you really mean 'kubernetes'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'kubernetes'?", "location": {"path": "mission-control/docs/topology/examples/prometheus.md", "range": {"start": {"line": 5, "column": 95}}}, "severity": "ERROR"}
Check failure on line 5 in mission-control/docs/topology/examples/prometheus.md
github-actions / vale
[vale] mission-control/docs/topology/examples/prometheus.md#L5
[Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'namespace' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/examples/prometheus.md", "range": {"start": {"line": 5, "column": 131}}}, "severity": "ERROR"}
Check failure on line 5 in mission-control/docs/topology/examples/prometheus.md
github-actions / vale
[vale] mission-control/docs/topology/examples/prometheus.md#L5
[Vale.Spelling] Did you really mean 'namespace'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'namespace'?", "location": {"path": "mission-control/docs/topology/examples/prometheus.md", "range": {"start": {"line": 5, "column": 131}}}, "severity": "ERROR"}
Check failure on line 5 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L5
[Vale.Spelling] Did you really mean 'configs'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'configs'?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 5, "column": 30}}}, "severity": "ERROR"}
Check failure on line 5 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L5
[Flanksource.Spelling] Is 'configs' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'configs' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 5, "column": 30}}}, "severity": "ERROR"}
Check failure on line 5 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L5
[Vale.Spelling] Did you really mean 'config'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'config'?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 5, "column": 50}}}, "severity": "ERROR"}
Check failure on line 5 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L5
[Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 5, "column": 50}}}, "severity": "ERROR"}
Check failure on line 7 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L7
[Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 7, "column": 59}}}, "severity": "ERROR"}
Check failure on line 7 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L7
[Vale.Spelling] Did you really mean 'config'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'config'?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 7, "column": 59}}}, "severity": "ERROR"}
Check failure on line 9 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L9
[Vale.Spelling] Did you really mean 'Config'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'Config'?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 9, "column": 13}}}, "severity": "ERROR"}
Check failure on line 9 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L9
[Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 9, "column": 13}}}, "severity": "ERROR"}
Check failure on line 30 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L30
[Vale.Spelling] Did you really mean 'Config'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'Config'?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 30, "column": 4}}}, "severity": "ERROR"}
Check failure on line 30 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L30
[Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'Config' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 30, "column": 4}}}, "severity": "ERROR"}
Check failure on line 34 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L34
[Vale.Spelling] Did you really mean 'config'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'config'?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 34, "column": 43}}}, "severity": "ERROR"}
Check failure on line 34 in mission-control/docs/topology/concepts/catalog.md
github-actions / vale
[vale] mission-control/docs/topology/concepts/catalog.md#L34
[Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'config' spelled correctly? Is it missing code formatting?", "location": {"path": "mission-control/docs/topology/concepts/catalog.md", "range": {"start": {"line": 34, "column": 43}}}, "severity": "ERROR"}