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/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/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/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/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| [Flanksource.Spelling] Is 'Kustomization' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/catalog.mdx|38 col 48| [Flanksource.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/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/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| [alex.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|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|75 col 38| [Flanksource.Spelling] Is 'XPath' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/sql.mdx|55 col 45| [Flanksource.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| [Flanksource.Spelling] Is 'stderr' spelled correctly? Is it missing code formatting?
mission-control/docs/topology/lookups/exec.md|54 col 87| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
mission-control/docs/topology/lookups/exec.md|54 col 108| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
mission-control/docs/topology/lookups/exec.md|54 col 156| [Flanksource.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|66 col 16| [Flanksource.Spelling] Is 'stderr' 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|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/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/index.mdx|49 col 5| [Flanksource.Spelling] Is 'forEach' 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/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/partials/_gotemplate.md|29 col 25| [Flanksource.Spelling] Is 'multiline' spelled correctly? Is it missing code formatting?
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/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|53 col 3| [Flanksource.Spelling] Is 'fieldSelector' spelled correctly? Is it missing code formatting?
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/scripting/_functions.md|65 col 192| [Flanksource.Spelling] Is 'tim' spelled correctly? Is it missing code formatting?
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 52| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/topology/index.mdx|40 col 16| [Flanksource.Spelling] Is 'Gotemplate' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/index.mdx|49 col 85| [Flanksource.Spelling] Is 'gcp' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/index.mdx|49 col 134| [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/index.mdx|50 col 45| [Flanksource.Spelling] Is 'gcp' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/index.mdx|55 col 67| [Flanksource.Spelling] Is 'toplogy' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/properties.md|12 col 24| [Flanksource.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 54| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/topology/properties.md|44 col 46| [Flanksource.Adverbs] Consider removing 'rarely'.
mission-control/docs/reference/topology/components.mdx|16 col 89| [Flanksource.Spelling] Is 'Unmarshaler' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/components.mdx|18 col 123| [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/components.mdx|22 col 84| [Flanksource.Spelling] Is 'dev' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/components.mdx|31 col 55| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/resource-selector.md|24 col 98| [Vale.Repetition] 'are' is repeated!
mission-control/docs/reference/resource-selector.md|24 col 110| [Flanksource.Adverbs] Consider removing 'very'.
mission-control/docs/reference/helm/mission-control.mdx|8 col 8| [Flanksource.Spelling] Is 'const' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/helm/mission-control.mdx|8 col 14| [Flanksource.Spelling] Is 'toc' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/connections/Notifications/smtp.mdx|48 col 32| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/connections/Notifications/smtp.mdx|67 col 13| [Flanksource.Spelling] Is 'toAddresses' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/connections/index.mdx|6 col 20| [alex.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/reference/connections/index.mdx|6 col 20| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easy'.
mission-control/docs/reference/connections/index.mdx|6 col 20| [Flanksource.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/reference/connections/index.mdx|86 col 26| [Flanksource.Spelling] Is 'datasource' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/connections/Notifications/slack.mdx|44 col 14| [Flanksource.Spelling] Is 'botName' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/connections/Notifications/slack.mdx|47 col 13| [Flanksource.ProfanityUnlikely] Be careful with 'color', it's profane in some cases.
mission-control/docs/reference/connections/Notifications/slack.mdx|48 col 44| [Flanksource.ProfanityUnlikely] Be careful with 'color', it's profane in some cases.
mission-control/docs/reference/connections/Notifications/slack.mdx|49 col 56| [Flanksource.ProfanityUnlikely] Be careful with 'color', it's profane in some cases.
mission-control/docs/reference/connections/Notifications/slack.mdx|54 col 16| [Flanksource.Spelling] Is 'icon_emoji' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/connections/Notifications/slack.mdx|54 col 30| [Flanksource.Spelling] Is 'icon_url' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/connections/Notifications/slack.mdx|62 col 19| [Flanksource.Spelling] Is 'Prepended' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/connections/git.md|49 col 1| [Flanksource.Wordiness] Consider using 'to' instead of 'In order to'.
mission-control/docs/reference/notifications/template_functions.mdx|5 col 1| [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/reference/notifications/template_functions.mdx|7 col 4| [Flanksource.Spelling] Is 'labelsFormat' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/template_functions.mdx|34 col 30| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/notifications/_notification.mdx|35 col 52| [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/reference/notifications/_notification.mdx|39 col 13| [Flanksource.Spelling] Is 'repeatInterval' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_notification.mdx|40 col 79| [Flanksource.Spelling] Is 'succefully' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_notification.mdx|44 col 13| [Flanksource.Spelling] Is 'repeatGroup' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_notification.mdx|52 col 5| [Flanksource.Spelling] Is 'templateEnv' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_notification.mdx|62 col 5| [Flanksource.Spelling] Is 'templateEnv' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_notification.mdx|70 col 124| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/notifications/_notification.mdx|72 col 5| [Flanksource.Spelling] Is 'templateEnv' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/env-var.mdx|19 col 7| [Flanksource.Spelling] Is 'inlining' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/env-var.mdx|154 col 90| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/env-var.mdx|190 col 44| [Flanksource.Spelling] Is 'unencrypted' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/env-var.mdx|190 col 99| [Flanksource.Spelling] Is 'etcd' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/env-var.mdx|190 col 195| [Flanksource.Spelling] Is 'etcd' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/env-var.mdx|194 col 4| [Flanksource.Spelling] Is 'Bitnami' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/config-db/config.md|25 col 81| [Flanksource.Spelling] Is 'undeleted' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/config-db/properties.md|13 col 20| [Flanksource.ProfanityUnlikely] Be careful with 'color', it's profane in some cases.
mission-control/docs/reference/config-db/properties.md|17 col 26| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/config-db/properties.md|21 col 50| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/playbooks/parameters.md|36 col 73| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/playbooks/parameters.md|36 col 81| [Flanksource.Spelling] Is 'prepopulated' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/playbooks/parameters.md|88 col 26| [Flanksource.Spelling] Is 'multiline' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/playbooks/parameters.md|88 col 36| [Flanksource.Spelling] Is 'textarea' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/playbooks/index.md|65 col 36| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
mission-control/docs/reference/playbooks/index.md|82 col 71| [Flanksource.Spelling] Is 'CLI's' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|64 col 19| [Flanksource.Spelling] Is 'new_state' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|114 col 19| [Flanksource.Spelling] Is 'config_class' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|124 col 19| [Flanksource.Spelling] Is 'created_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|129 col 19| [Flanksource.Spelling] Is 'delete_reason' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|134 col 19| [Flanksource.Spelling] Is 'deleted_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|144 col 19| [Flanksource.Spelling] Is 'external_id' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|174 col 19| [Flanksource.Spelling] Is 'scraper_id' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|199 col 19| [Flanksource.Spelling] Is 'updated_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|236 col 19| [Flanksource.Spelling] Is 'created_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|241 col 19| [Flanksource.Spelling] Is 'updated_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|246 col 19| [Flanksource.Spelling] Is 'deleted_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|268 col 19| [Flanksource.Spelling] Is 'external_id' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|308 col 19| [Flanksource.Spelling] Is 'status_reason' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|328 col 19| [Flanksource.Spelling] Is 'topology_type' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|338 col 19| [Flanksource.Spelling] Is 'cost_per_minute' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|363 col 19| [Flanksource.Spelling] Is 'created_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|368 col 19| [Flanksource.Spelling] Is 'updated_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|373 col 19| [Flanksource.Spelling] Is 'deleted_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|435 col 19| [Flanksource.Spelling] Is 'last_runtime' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|440 col 19| [Flanksource.Spelling] Is 'next_runtime' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|445 col 19| [Flanksource.Spelling] Is 'last_transition_time' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|450 col 19| [Flanksource.Spelling] Is 'created_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|455 col 19| [Flanksource.Spelling] Is 'updated_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|460 col 19| [Flanksource.Spelling] Is 'deleted_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|488 col 21| [Flanksource.Spelling] Is 'last_pass' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|493 col 21| [Flanksource.Spelling] Is 'last_fail' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|538 col 36| [Flanksource.Spelling] Is 'errored' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|561 col 21| [Flanksource.Ablist] When referring to a person, consider using 'turned off', 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'invalid'.
mission-control/docs/reference/notifications/_env_vars.mdx|563 col 45| [Flanksource.Spelling] Is 'errored' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/notifications/_env_vars.mdx|586 col 21| [Flanksource.Spelling] Is 'created_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/playbooks/context.mdx|26 col 37| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
mission-control/docs/reference/playbooks/context.mdx|29 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/reference/playbooks/context.mdx|49 col 5| [Flanksource.Spelling] Is 'apiVersion' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/playbooks/context.mdx|55 col 22| [Flanksource.Spelling] Is 'Kustomize' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/playbooks/context.mdx|60 col 17| [Flanksource.Spelling] Is 'commit_message' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/playbooks/context.mdx|67 col 164| [Flanksource.Spelling] Is 'eg' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/playbooks/context.mdx|82 col 65| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'just'.
mission-control/docs/canary-checker/scripting/_functions.md|65 col 192| [Flanksource.Spelling] Is 'tim' spelled correctly? Is it missing code formatting?
mission-control/docs/canary-checker/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/canary-checker/reference/3-containerd.mdx|9 col 12| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/canary-checker/reference/3-containerd.mdx|66 col 12| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/canary-checker/reference/1-exec.mdx|23 col 87| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
mission-control/docs/canary-checker/reference/1-exec.mdx|23 col 108| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
mission-control/docs/canary-checker/reference/1-exec.mdx|23 col 156| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
mission-control/docs/canary-checker/reference/1-exec.mdx|43 col 51| [Flanksource.Spelling] Is 'eg' spelled correctly? Is it missing code formatting?
mission-control/docs/canary-checker/reference/1-exec.mdx|61 col 1| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/canary-checker/reference/1-exec.mdx|107 col 169| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|8 col 61| [Flanksource.Adverbs] Consider removing 'quickly'.
mission-control/docs/reference/scripting/cel.mdx|46 col 142| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|444 col 210| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|455 col 132| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|511 col 34| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|566 col 71| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|725 col 32| [Flanksource.Spelling] Is 'eturns' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/cel.mdx|1014 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/reference/scripting/cel.mdx|1015 col 33| [alex.ProfanityMaybe] Reconsider using 'addict', it may be profane.
mission-control/docs/reference/scripting/cel.mdx|1015 col 33| [Flanksource.Ablist] When referring to a person, consider using 'person with a drug addiction' or 'person recovering from a drug addiction' instead of 'addict'.
mission-control/docs/reference/scripting/cel.mdx|1038 col 31| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|1524 col 134| [Flanksource.Ablist] When referring to a person, consider using 'turned off', 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'invalid'.
mission-control/docs/reference/scripting/cel.mdx|1545 col 169| [Flanksource.Ablist] When referring to a person, consider using 'turned off', 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'invalid'.
mission-control/docs/reference/scripting/cel.mdx|1649 col 231| [Flanksource.Ablist] When referring to a person, consider using 'turned off', 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'invalid'.
mission-control/docs/reference/scripting/cel.mdx|1682 col 145| [Flanksource.Ablist] When referring to a person, consider using 'turned off', 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'invalid'.
mission-control/docs/reference/scripting/cel.mdx|1712 col 66| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|1713 col 101| [Flanksource.Brevity] Avoid statements that don't add clarity, like 'Note that'.
mission-control/docs/reference/scripting/cel.mdx|1714 col 117| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|1716 col 12| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|1762 col 53| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|1799 col 8| [Flanksource.Brevity] Avoid statements that don't add clarity, like 'Note that'.
mission-control/docs/reference/scripting/cel.mdx|1799 col 26| [Flanksource.ProfanityUnlikely] Be careful with 'period', it's profane in some cases.
mission-control/docs/reference/scripting/cel.mdx|1799 col 51| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|1804 col 98| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/cel.mdx|1962 col 8| [Flanksource.Ablist] When referring to a person, consider using 'turned off', 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'invalid'.
mission-control/docs/reference/scripting/cel.mdx|2024 col 59| [Flanksource.Wordiness] Consider using 'to' instead of 'in order to'.
mission-control/docs/reference/scripting/cel.mdx|2048 col 50| [Flanksource.Adverbs] Consider removing 'safely'.
mission-control/docs/reference/scripting/cel.mdx|2398 col 68| [alex.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/reference/scripting/cel.mdx|2398 col 68| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easy'.
mission-control/docs/reference/scripting/cel.mdx|2398 col 68| [Flanksource.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/reference/scripting/cel.mdx|2449 col 63| [alex.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/reference/scripting/cel.mdx|2449 col 63| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easy'.
mission-control/docs/reference/scripting/cel.mdx|2449 col 63| [Flanksource.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/canary-checker/reference/1-pod.mdx|19 col 56| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/canary-checker/reference/1-pod.mdx|21 col 61| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/canary-checker/reference/1-pod.mdx|22 col 62| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/canary-checker/reference/1-pod.mdx|32 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/canary-checker/reference/1-http.mdx|31 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/canary-checker/reference/1-http.mdx|121 col 28| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|48 col 89| [Flanksource.Wordiness] Consider using 'whether' instead of 'whether or not'.
mission-control/docs/reference/scripting/gotemplate.mdx|127 col 10| [Flanksource.SpellingSuggestions] Use 'data type(s)' instead of 'datatype'.
mission-control/docs/reference/scripting/gotemplate.mdx|149 col 10| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|162 col 12| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|224 col 185| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|224 col 190| [Flanksource.Condescending] Using 'simply' may come across as condescending.
mission-control/docs/reference/scripting/gotemplate.mdx|224 col 190| [alex.Condescending] Using 'simply' may come across as condescending.
mission-control/docs/reference/scripting/gotemplate.mdx|224 col 190| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simply'.
mission-control/docs/reference/scripting/gotemplate.mdx|310 col 6| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|310 col 76| [Flanksource.Foreign] Use 'that is' instead of 'i.e.'.
mission-control/docs/reference/scripting/gotemplate.mdx|520 col 11| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|555 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/reference/scripting/gotemplate.mdx|555 col 97| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'Will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|573 col 67| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|628 col 47| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|695 col 10| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'obviously'.
mission-control/docs/reference/scripting/gotemplate.mdx|695 col 10| [Flanksource.Condescending] Using 'obviously' may come across as condescending.
mission-control/docs/reference/scripting/gotemplate.mdx|695 col 10| [alex.Condescending] Using 'obviously' may come across as condescending.
mission-control/docs/reference/scripting/gotemplate.mdx|824 col 68| [Flanksource.Spelling] Is 'diretory' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/gotemplate.mdx|855 col 113| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/reference/scripting/gotemplate.mdx|863 col 89| [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)