styles/alex/README.md|1 col 11| [Flanksource.Spelling] Is 'alex' spelled correctly? Is it missing code formatting?
mission-control/README.md|3 col 30| [Flanksource.Spelling] Is 'Docusaurus' spelled correctly? Is it missing code formatting?
mission-control/static/img/getting-started.mdx|71 col 60| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/static/img/getting-started.mdx|88 col 25| [Flanksource.Exclamation] Don't use exclamation points in text.
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/connections/git.md|49 col 1| [Flanksource.Wordiness] Consider using 'to' instead of 'In order to'.
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| [alex.Condescending] Using 'easy' may come across as condescending.
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/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/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|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/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|32 col 19| [Flanksource.Spelling] Is 'external_id' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/components.mdx|62 col 19| [Flanksource.Spelling] Is 'status_reason' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/components.mdx|87 col 19| [Flanksource.Spelling] Is 'topology_type' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/components.mdx|98 col 19| [Flanksource.Spelling] Is 'cost_per_minute' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/components.mdx|123 col 19| [Flanksource.Spelling] Is 'created_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/components.mdx|129 col 19| [Flanksource.Spelling] Is 'updated_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/components.mdx|134 col 19| [Flanksource.Spelling] Is 'deleted_at' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/crd.mdx|22 col 52| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/topology/crd.mdx|23 col 52| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
mission-control/docs/reference/topology/crd.mdx|45 col 16| [Flanksource.Spelling] Is 'Gotemplate' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/crd.mdx|54 col 85| [Flanksource.Spelling] Is 'gcp' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/crd.mdx|54 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/crd.mdx|55 col 45| [Flanksource.Spelling] Is 'gcp' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/crd.mdx|60 col 67| [Flanksource.Spelling] Is 'toplogy' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/crd.mdx|91 col 89| [Flanksource.Spelling] Is 'Unmarshaler' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/crd.mdx|93 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/crd.mdx|97 col 84| [Flanksource.Spelling] Is 'dev' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/topology/crd.mdx|106 col 55| [Flanksource.Wordiness] Consider using 'about' instead of 'pertaining to'.
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/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/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|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|80 col 65| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'just'.
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/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|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/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/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/architecture.mdx|27 col 68| [Flanksource.Adverbs] Consider removing 'heavily'.
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/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|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/installation/_agent_properties.mdx|39 col 115| [Flanksource.Spelling] Is 'disovered' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_agent_properties.mdx|41 col 51| [Flanksource.Wordiness] Consider using 'usually' instead of 'in most cases'.
mission-control/docs/installation/self-hosted/database.md|46 col 1| [Flanksource.Wordiness] Consider using 'to' instead of 'In order to'.
mission-control/docs/installation/self-hosted/database.md|50 col 37| [Flanksource.Spelling] Is 'kratos' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/artifacts.md|15 col 18| [Flanksource.Spelling] Is 'filestores' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/artifacts.md|15 col 233| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simply'.
mission-control/docs/installation/artifacts.md|15 col 233| [alex.Condescending] Using 'simply' may come across as condescending.
mission-control/docs/installation/artifacts.md|15 col 233| [Flanksource.Condescending] Using 'simply' may come across as condescending.
mission-control/docs/installation/self-hosted/oidc.mdx|8 col 23| [Flanksource.Spelling] Is 'kratos' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/oidc.mdx|14 col 14| [Flanksource.Spelling] Is 'Entra' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/oidc.mdx|17 col 23| [Flanksource.Spelling] Is 'Entra' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/oidc.mdx|31 col 5| [Flanksource.Spelling] Is 'Jsonnet' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/oidc.mdx|52 col 13| [Flanksource.Spelling] Is 'Entra' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/oidc.mdx|56 col 52| [Flanksource.Spelling] Is 'jsonnet' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/getting-started.mdx|10 col 8| [Flanksource.Spelling] Is 'const' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/getting-started.mdx|10 col 14| [Flanksource.Spelling] Is 'toc' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/getting-started.mdx|38 col 10| [Flanksource.Spelling] Is 'smtp' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/getting-started.mdx|43 col 10| [Flanksource.Spelling] Is 'sso' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/getting-started.mdx|62 col 9| [Flanksource.Spelling] Is 'CPUs' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/getting-started.mdx|70 col 13| [Flanksource.Spelling] Is 'routable' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/getting-started.mdx|72 col 76| [Flanksource.Spelling] Is 'minikube' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/self-hosted/getting-started.mdx|72 col 95| [Flanksource.Spelling] Is 'routable' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_ingress.mdx|6 col 65| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/installation/_aws_iam.mdx|15 col 39| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'just'.
mission-control/docs/installation/_aws_iam.mdx|86 col 23| [Flanksource.Spelling] Is 'sts' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_aws_iam.mdx|137 col 2| [Flanksource.Spelling] Is 'serviceAccount' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_aws_iam.mdx|143 col 3| [Flanksource.Spelling] Is 'serviceAccount' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_aws_iam.mdx|145 col 16| [Flanksource.Spelling] Is 'cloudwatch' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_aws_iam.mdx|149 col 3| [Flanksource.Spelling] Is 'serviceAccount' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_aws_iam.mdx|272 col 13| [Flanksource.Spelling] Is 'cloudformation' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/saas/getting-started.mdx|9 col 8| [Flanksource.Spelling] Is 'const' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/saas/getting-started.mdx|9 col 14| [Flanksource.Spelling] Is 'toc' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/saas/getting-started.mdx|10 col 17| [Flanksource.Spelling] Is 'Signup' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/saas/getting-started.mdx|11 col 14| [Flanksource.Spelling] Is 'signup' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/saas/getting-started.mdx|42 col 5| [Flanksource.Spelling] Is 'Signup' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/saas/getting-started.mdx|43 col 4| [Flanksource.Spelling] Is 'Goto' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/saas/getting-started.mdx|43 col 89| [Flanksource.Spelling] Is 'signup' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|17 col 1| [Flanksource.Wordiness] Consider using 'to' instead of 'In order to'.
mission-control/docs/installation/_properties_db.mdx|44 col 1| [Flanksource.Wordiness] Consider using 'to' instead of 'In order to'.
mission-control/docs/installation/_properties_db.mdx|66 col 3| [Flanksource.Spelling] Is 'max_connections' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|67 col 3| [Flanksource.Spelling] Is 'shared_buffers' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|68 col 3| [Flanksource.Spelling] Is 'effective_cache_size' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|69 col 3| [Flanksource.Spelling] Is 'maintenance_work_mem' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|70 col 3| [Flanksource.Spelling] Is 'wal_buffers' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|71 col 3| [Flanksource.Spelling] Is 'effective_io_concurrency' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|72 col 3| [Flanksource.Spelling] Is 'work_mem' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|73 col 3| [Flanksource.Spelling] Is 'max_wal_size' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|74 col 3| [Flanksource.Spelling] Is 'log_autovacuum_min_duration' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|75 col 3| [Flanksource.Spelling] Is 'log_connections' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|76 col 3| [Flanksource.Spelling] Is 'log_destination' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|77 col 3| [Flanksource.Spelling] Is 'log_directory' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|78 col 3| [Flanksource.Spelling] Is 'log_file_mode' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|79 col 3| [Flanksource.Spelling] Is 'log_filename' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|80 col 3| [Flanksource.Spelling] Is 'log_line_prefix' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|81 col 3| [Flanksource.Spelling] Is 'log_lock_waits' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|82 col 3| [Flanksource.Spelling] Is 'log_min_duration_statement' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|83 col 3| [Flanksource.Spelling] Is 'log_rotation_age' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|84 col 3| [Flanksource.Spelling] Is 'log_rotation_size' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|85 col 3| [Flanksource.Spelling] Is 'log_statement' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|86 col 3| [Flanksource.Spelling] Is 'log_temp_files' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|87 col 3| [Flanksource.Spelling] Is 'log_timezone' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|88 col 3| [Flanksource.Spelling] Is 'logging_collector' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|89 col 3| [Flanksource.Spelling] Is 'ssl' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|91 col 3| [Flanksource.Spelling] Is 'password_encryption' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|92 col 3| [Flanksource.Spelling] Is 'db_user_namespace' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|93 col 3| [Flanksource.Spelling] Is 'extra_float_digits' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|96 col 5| [Flanksource.Spelling] Is 'Pganalyze' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|105 col 75| [Flanksource.Spelling] Is 'pganalyze' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|108 col 5| [Flanksource.Spelling] Is 'Postgrest' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|112 col 23| [Flanksource.Spelling] Is 'postgrest' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/_properties_db.mdx|123 col 34| [Flanksource.Spelling] Is 'Postgrest' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/scripting/cel.mdx|8 col 61| [Flanksource.Adverbs] Consider removing 'quickly'.
mission-control/docs/reference/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'.
mission-control/docs/reference/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'.
mission-control/docs/reference/scripting/cel.mdx|627 col 32| [Flanksource.Spelling] Is 'eturns' spelled correctly? Is it missing code formatting?
mission-control/docs/reference/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'.
mission-control/docs/reference/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'.
mission-control/docs/reference/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'.
mission-control/docs/reference/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'.
mission-control/docs/reference/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'.
mission-control/docs/reference/scripting/cel.mdx|1701 col 16| [Flanksource.ProfanityUnlikely] Be careful with 'period', it's profane in some cases.
mission-control/docs/reference/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'.
mission-control/docs/reference/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'.
mission-control/docs/reference/scripting/cel.mdx|1926 col 59| [Flanksource.Wordiness] Consider using 'to' instead of 'in order to'.
mission-control/docs/reference/scripting/cel.mdx|1950 col 50| [Flanksource.Adverbs] Consider removing 'safely'.
mission-control/docs/reference/scripting/cel.mdx|2300 col 68| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easy'.
mission-control/docs/reference/scripting/cel.mdx|2300 col 68| [alex.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/reference/scripting/cel.mdx|2300 col 68| [Flanksource.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/reference/scripting/cel.mdx|2351 col 63| [Flanksource.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/reference/scripting/cel.mdx|2351 col 63| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easy'.
mission-control/docs/reference/scripting/cel.mdx|2351 col 63| [alex.Condescending] Using 'easy' may come across as condescending.
mission-control/docs/installation/local-testing.md|13 col 63| [Flanksource.Spelling] Is 'minikube' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/local-testing.md|45 col 23| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/installation/local-testing.md|45 col 104| [Flanksource.Spelling] Is 'hostPort' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/local-testing.md|63 col 1| [Flanksource.CaseSensitiveSpellingSuggestions] Use 'NGINX Ingress Controller' instead of 'nginx ingress controller'.
mission-control/docs/installation/local-testing.md|65 col 16| [Flanksource.CaseSensitiveSpellingSuggestions] Use 'NGINX Ingress Controller' instead of 'Nginx Ingress Controller'.
mission-control/docs/installation/local-testing.md|104 col 2| [alex.ProfanityLikely] Don't use 'nip', it's profane.
mission-control/docs/installation/local-testing.md|104 col 28| [alex.Condescending] Using 'simple' may come across as condescending.
mission-control/docs/installation/local-testing.md|104 col 28| [Flanksource.Condescending] Using 'simple' may come across as condescending.
mission-control/docs/installation/local-testing.md|104 col 28| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simple'.
mission-control/docs/installation/local-testing.md|111 col 10| [alex.ProfanityLikely] Don't use 'nip', it's profane.
mission-control/docs/installation/local-testing.md|111 col 18| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/installation/local-testing.md|158 col 63| [Flanksource.Spelling] Is 'retrived' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/local-testing.md|166 col 14| [Flanksource.Spelling] Is 'goto' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/local-testing.md|169 col 56| [Flanksource.CaseSensitiveSpellingSuggestions] Use 'nginx' instead of 'Nginx'.
mission-control/docs/installation/local-testing.md|196 col 10| [Flanksource.Spelling] Is 'goto' spelled correctly? Is it missing code formatting?
mission-control/docs/external-postgres.md|26 col 32| [Flanksource.Spelling] Is 'hstore' spelled correctly? Is it missing code formatting?
mission-control/docs/external-postgres.md|28 col 27| [Flanksource.Spelling] Is 'postgrest_anon' spelled correctly? Is it missing code formatting?
mission-control/docs/external-postgres.md|30 col 27| [Flanksource.Spelling] Is 'postgrest_api' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/deployment-models.mdx|7 col 8| [Flanksource.Spelling] Is 'const' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/deployment-models.mdx|7 col 14| [Flanksource.Spelling] Is 'toc' spelled correctly? Is it missing code formatting?
mission-control/docs/installation/deployment-models.mdx|56 col 3| [Flanksource.ProfanityUnlikely] Be careful with 'Pros', it's profane in some cases.
mission-control/docs/installation/deployment-models.mdx|72 col 104| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/installation/deployment-models.mdx|72 col 155| [Flanksource.Wordiness] Consider using 'sometimes' instead of 'in some cases'.
mission-control/docs/installation/deployment-models.mdx|76 col 3| [Flanksource.ProfanityUnlikely] Be careful with 'Pros', it's profane in some cases.
mission-control/docs/installation/deployment-models.mdx|95 col 92| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
mission-control/docs/installation/deployment-models.mdx|98 col 3| [Flanksource.ProfanityUnlikely] Be careful with 'Pros', it's profane in some cases.
mission-control/docs/installation/deployment-models.mdx|123 col 3| [Flanksource.ProfanityUnlikely] Be careful with 'Pros', it's profane in some cases.
mission-control/docs/installation/deployment-models.mdx|139 col 3| [Flanksource.ProfanityUnlikely] Be careful with 'Pros', it's profane in some cases.
mission-control/docs/installation/deployment-models.mdx|142 col 41| [Flanksource.Spelling] Is 'enviroments' spelled correctly? Is it missing code formatting?
mission-control/docs/index.mdx|70 col 116| [Flanksource.Spelling] Is 'Minukube' spelled correctly? Is it missing code formatting?
mission-control/docs/index.mdx|84 col 25| [Flanksource.Exclamation] Don't use exclamation points in text.
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'.
... (Too many findings. Dropped some findings)