Skip to content

chore: use normal sort order

Sign in for the full log view
GitHub Actions / vale completed Sep 4, 2024 in 15s

reviewdog [vale] report

reported by reviewdog 🐶

Findings (1024)

canary-checker/docs/database.md|48 col 123| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/prereqs.md|3 col 114| [Flanksource.Adverbs] Consider removing 'strictly'.
canary-checker/tutorials/prereqs.md|7 col 16| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'obvious'.
canary-checker/tutorials/prereqs.md|7 col 16| [alex.Condescending] Using 'obvious' may come across as condescending.
canary-checker/tutorials/prereqs.md|7 col 16| [Flanksource.Condescending] Using 'obvious' may come across as condescending.
canary-checker/tutorials/prereqs.md|7 col 223| [Flanksource.Adverbs] Consider removing 'properly'.
canary-checker/tutorials/prereqs.md|19 col 13| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/prereqs.md|52 col 281| [Flanksource.FirstPerson] Do not use the first person (such as ' I ').
canary-checker/tutorials/prereqs.md|85 col 1| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'You'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/dev-guide.md|1 col 3| [Flanksource.Spelling] Is 'Dev' spelled correctly? Is it missing code formatting?
canary-checker/tutorials/dev-guide.md|9 col 15| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'we'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/dev-guide.md|22 col 68| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/dev-guide.md|24 col 12| [Flanksource.Spelling] Is 'nvm' spelled correctly? Is it missing code formatting?
canary-checker/tutorials/dev-guide.md|25 col 9| [Flanksource.Spelling] Is 'nvm' spelled correctly? Is it missing code formatting?
canary-checker/tutorials/dev-guide.md|33 col 25| [Flanksource.Spelling] Is 'distro' spelled correctly? Is it missing code formatting?
canary-checker/tutorials/dev-guide.md|37 col 19| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/dev-guide.md|39 col 74| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'they'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/dev-guide.md|70 col 18| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/comparisons/blackbox-exporter.md|3 col 136| [Flanksource.SerialComma] Use a serial comma in 'TCP, ICMP and gRPC.'.
canary-checker/docs/getting-started.mdx|83 col 60| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/getting-started.mdx|99 col 25| [Flanksource.Exclamation] Don't use exclamation points in text.
canary-checker/docs/reference/1-sql.mdx|9 col 12| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/1-alert-manager.mdx|11 col 180| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/1-elasticsearch.mdx|7 col 12| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/1-elasticsearch.mdx|31 col 40| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
canary-checker/docs/reference/_connections.mdx|144 col 18| [Flanksource.Spelling] Is 'utually' spelled correctly? Is it missing code formatting?
canary-checker/docs/reference/1-exec.mdx|23 col 87| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
canary-checker/docs/reference/1-exec.mdx|23 col 108| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
canary-checker/docs/reference/1-exec.mdx|23 col 156| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
canary-checker/docs/reference/1-exec.mdx|43 col 51| [Flanksource.Spelling] Is 'eg' spelled correctly? Is it missing code formatting?
canary-checker/docs/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'.
canary-checker/docs/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'.
canary-checker/docs/reference/jmeter.mdx|10 col 12| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/jmeter.mdx|36 col 67| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
canary-checker/tutorials/getting-started.md|5 col 58| [Flanksource.Adverbs] Consider removing 'continually'.
canary-checker/tutorials/getting-started.md|7 col 16| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'you'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|17 col 24| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|17 col 42| [Flanksource.Adverbs] Consider removing 'quickly'.
canary-checker/tutorials/getting-started.md|17 col 54| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simply'.
canary-checker/tutorials/getting-started.md|17 col 54| [alex.Condescending] Using 'simply' may come across as condescending.
canary-checker/tutorials/getting-started.md|17 col 54| [Flanksource.Condescending] Using 'simply' may come across as condescending.
canary-checker/tutorials/getting-started.md|51 col 1| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'You'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|51 col 49| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|51 col 130| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'you'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|55 col 76| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|57 col 74| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|57 col 181| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|109 col 1| [Flanksource.Brevity] Avoid statements that don't add clarity, like 'You can see that'.
canary-checker/tutorials/getting-started.md|112 col 23| [Flanksource.Condescending] Using 'simple' may come across as condescending.
canary-checker/tutorials/getting-started.md|112 col 23| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simple'.
canary-checker/tutorials/getting-started.md|112 col 23| [alex.Condescending] Using 'simple' may come across as condescending.
canary-checker/tutorials/getting-started.md|140 col 80| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'you'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/tutorials/getting-started.md|184 col 51| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simple'.
canary-checker/tutorials/getting-started.md|184 col 51| [alex.Condescending] Using 'simple' may come across as condescending.
canary-checker/tutorials/getting-started.md|184 col 51| [Flanksource.Condescending] Using 'simple' may come across as condescending.
canary-checker/tutorials/getting-started.md|223 col 20| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'You'll'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/3-namespace.mdx|64 col 59| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/3-namespace.mdx|70 col 42| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/3-namespace.mdx|72 col 41| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/3-restic.mdx|22 col 56| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/1-git.mdx|24 col 46| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
canary-checker/docs/reference/3-gcs-database-backup.mdx|27 col 47| [Flanksource.Spelling] Is 'eg' spelled correctly? Is it missing code formatting?
canary-checker/docs/reference/1-icmp.mdx|7 col 62| [Flanksource.SerialComma] Use a serial comma in 'loss, duration and response.'.
canary-checker/docs/reference/1-kubernetes.mdx|18 col 53| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/reference/1-junit.mdx|69 col 54| [Flanksource.Spelling] Is 'atest' spelled correctly? Is it missing code formatting?
canary-checker/docs/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'.
canary-checker/docs/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'.
canary-checker/docs/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'.
canary-checker/docs/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'.
canary-checker/docs/reference/1-folder.mdx|7 col 37| [Flanksource.SerialComma] Use a serial comma in 'size, age and count.'.
canary-checker/docs/reference/1-folder.mdx|46 col 40| [Flanksource.Spelling] Is 'maximim' spelled correctly? Is it missing code formatting?
canary-checker/docs/troubleshooting.mdx|28 col 30| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/troubleshooting.mdx|54 col 18| [Flanksource.Spelling] Is 'fom' spelled correctly? Is it missing code formatting?
canary-checker/docs/troubleshooting.mdx|93 col 21| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/troubleshooting.mdx|93 col 116| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/troubleshooting.mdx|129 col 25| [Flanksource.Spelling] Is 'loggined' spelled correctly? Is it missing code formatting?
canary-checker/docs/scripting/_functions.md|65 col 192| [Flanksource.Spelling] Is 'tim' spelled correctly? Is it missing code formatting?
canary-checker/docs/comparison.md|5 col 203| [Flanksource.Spelling] Is 'imcp' spelled correctly? Is it missing code formatting?
canary-checker/docs/comparison.md|26 col 450| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/comparison.md|26 col 554| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simple'.
canary-checker/docs/comparison.md|26 col 554| [alex.Condescending] Using 'simple' may come across as condescending.
canary-checker/docs/comparison.md|26 col 554| [Flanksource.Condescending] Using 'simple' may come across as condescending.
canary-checker/docs/comparison.md|28 col 194| [alex.Condescending] Using 'easily' may come across as condescending.
canary-checker/docs/comparison.md|28 col 194| [Flanksource.Condescending] Using 'easily' may come across as condescending.
canary-checker/docs/comparison.md|28 col 194| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easily'.
canary-checker/docs/comparison.md|30 col 425| [Flanksource.Adverbs] Consider removing 'really'.
canary-checker/docs/comparison.md|30 col 445| [alex.Condescending] Using 'easy' may come across as condescending.
canary-checker/docs/comparison.md|30 col 445| [Flanksource.Condescending] Using 'easy' may come across as condescending.
canary-checker/docs/comparison.md|30 col 445| [Flanksource.Exclamation] Don't use exclamation points in text.
canary-checker/docs/comparison.md|30 col 445| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'easy'.
canary-checker/docs/comparison.md|32 col 51| [Flanksource.Condescending] Using 'simple' may come across as condescending.
canary-checker/docs/comparison.md|32 col 51| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simple'.
canary-checker/docs/comparison.md|32 col 51| [alex.Condescending] Using 'simple' may come across as condescending.
canary-checker/docs/concepts/_artifacts.md|17 col 233| [alex.Condescending] Using 'simply' may come across as condescending.
canary-checker/docs/concepts/_artifacts.md|17 col 233| [Flanksource.Condescending] Using 'simply' may come across as condescending.
canary-checker/docs/concepts/_artifacts.md|17 col 233| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simply'.
canary-checker/docs/concepts/_artifacts.md|73 col 28| [Flanksource.Ablist] When referring to a person, consider using 'has a disability', 'person with a disability', or 'people with disabilities' instead of 'special'.
canary-checker/docs/concepts/secret-management.md|19 col 7| [Flanksource.Spelling] Is 'inlining' spelled correctly? Is it missing code formatting?
canary-checker/docs/concepts/secret-management.md|154 col 90| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/concepts/secret-management.md|190 col 44| [Flanksource.Spelling] Is 'unencrypted' spelled correctly? Is it missing code formatting?
canary-checker/docs/concepts/secret-management.md|190 col 99| [Flanksource.Spelling] Is 'etcd' spelled correctly? Is it missing code formatting?
canary-checker/docs/concepts/secret-management.md|190 col 195| [Flanksource.Spelling] Is 'etcd' spelled correctly? Is it missing code formatting?
canary-checker/docs/concepts/secret-management.md|194 col 4| [Flanksource.Spelling] Is 'Bitnami' spelled correctly? Is it missing code formatting?
canary-checker/docs/concepts/expressions/transforms.mdx|39 col 33| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/concepts/expressions/transforms.mdx|39 col 92| [Flanksource.Wordiness] Consider using 'all' instead of 'all of'.
canary-checker/docs/concepts/expressions/transforms.mdx|39 col 112| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/concepts/expressions/transforms.mdx|43 col 58| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/concepts/expressions/display-formatting.md|77 col 90| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'just'.
canary-checker/docs/concepts/expressions/health-evaluation.md|8 col 37| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/concepts/metrics/index.mdx|10 col 3| [Flanksource.Spelling] Is 'canary_check_success_count' spelled correctly? Is it missing code formatting?
canary-checker/docs/concepts/expressions/_transform_fields.mdx|17 col 13| [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'.
canary-checker/docs/concepts/expressions/_transform_fields.mdx|40 col 37| [Flanksource.Wordiness] Consider using 'during' instead of 'for the duration of'.
canary-checker/docs/concepts/expressions/_transform_fields.mdx|56 col 54| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/concepts/metrics/stateful-metrics.md|83 col 14| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/examples/k6.mdx|34 col 134| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/examples/k6.mdx|34 col 191| [Flanksource.Spelling] Is 'formating' spelled correctly? Is it missing code formatting?
canary-checker/docs/health-checks.mc.mdx|12 col 87| [Flanksource.SerialComma] Use a serial comma in 'services, infrastructure and applications.'.
canary-checker/docs/health-checks.mc.mdx|49 col 80| [Flanksource.SerialComma] Use a serial comma in 'services, infrastructure and applications.'.
canary-checker/docs/health-checks.mc.mdx|56 col 102| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/windows.md|32 col 268| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/windows.md|60 col 127| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/examples/sftp.mdx|7 col 47| [Flanksource.SerialComma] Use a serial comma in 'size, age and count.'.
canary-checker/docs/examples/smb.mdx|7 col 56| [Flanksource.SerialComma] Use a serial comma in 'size, age and count.'.
canary-checker/docs/examples/playwright.mdx|35 col 87| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/docs/examples/newman.mdx|35 col 83| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
SECURITY.md|14 col 10| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
SECURITY.md|16 col 57| [Flanksource.Exclamation] Don't use exclamation points in text.
styles/alex/README.md|1 col 11| [Flanksource.Spelling] Is 'alex' spelled correctly? Is it missing code formatting?
CONTRIBUTING.md|9 col 78| [Flanksource.Spelling] Is 'humands' spelled correctly? Is it missing code formatting?
CONTRIBUTING.md|13 col 21| [Flanksource.Spelling] Is 'Submenu' spelled correctly? Is it missing code formatting?
CONTRIBUTING.md|27 col 87| [Flanksource.Spelling] Is 'html' spelled correctly? Is it missing code formatting?
CONTRIBUTING.md|28 col 92| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
CONTRIBUTING.md|34 col 87| [Flanksource.Adverbs] Consider removing 'really'.
docs/incidents/concepts/done-definition.md|3 col 18| [Flanksource.Spelling] Is 'programatically' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/done-definition.md|13 col 73| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/incidents/concepts/done-definition.md|27 col 98| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/README.md|27 col 76| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/README.md|62 col 11| [Flanksource.Spelling] Is 'Formating' spelled correctly? Is it missing code formatting?
canary-checker/README.md|122 col 27| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
canary-checker/README.md|129 col 3| [Flanksource.Spelling] Is 'canary_check_success_count' spelled correctly? Is it missing code formatting?
canary-checker/README.md|140 col 3| [Flanksource.Spelling] Is 'canary_check_http_response_status' spelled correctly? Is it missing code formatting?
CONVENTIONS.md|2 col 19| [Flanksource.Spelling] Is 'salesy' spelled correctly? Is it missing code formatting?
CONVENTIONS.md|6 col 15| [Flanksource.Spelling] Is 'oxymorons' spelled correctly? Is it missing code formatting?
CONVENTIONS.md|11 col 130| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
CONVENTIONS.md|14 col 18| [Flanksource.Spelling] Is 'codeblocks' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|6 col 3| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|8 col 12| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|12 col 15| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|36 col 18| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|39 col 5| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|43 col 16| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|44 col 16| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|45 col 16| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|46 col 16| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/responders.md|47 col 16| [Flanksource.Spelling] Is 'Jira' spelled correctly? Is it missing code formatting?
docs/incidents/concepts/evidence.md|3 col 215| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/incidents/concepts/hypothesis.md|7 col 42| [Flanksource.Adverbs] Consider removing 'quickly'.
docs/apm-hub/backends/kubernetes.md|26 col 43| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/kubernetes.md|27 col 76| [Flanksource.Spelling] Is 'kubeconfig' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/kubernetes.md|27 col 105| [Flanksource.Spelling] Is 'kubeconfig' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/kubernetes.md|27 col 116| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/kubernetes.md|28 col 48| [Flanksource.Spelling] Is 'kubeconfig' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/opensearch.md|3 col 132| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/opensearch.md|55 col 42| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/opensearch.md|57 col 75| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/opensearch.md|57 col 99| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/opensearch.md|68 col 36| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/opensearch.md|69 col 36| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/opensearch.md|70 col 37| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/file.md|1 col 18| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/file.md|36 col 39| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/templating.md|5 col 3| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'Simply'.
docs/apm-hub/concepts/templating.md|5 col 3| [alex.Condescending] Using 'Simply' may come across as condescending.
docs/apm-hub/concepts/templating.md|5 col 3| [Flanksource.Condescending] Using 'Simply' may come across as condescending.
docs/apm-hub/concepts/templating.md|11 col 246| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/elasticsearch.md|3 col 132| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/elasticsearch.md|55 col 42| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/elasticsearch.md|57 col 75| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/elasticsearch.md|57 col 99| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/elasticsearch.md|62 col 17| [Flanksource.Spelling] Is 'APIKey' spelled correctly? Is it missing code formatting?
docs/apm-hub/backends/elasticsearch.md|72 col 36| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/backends/elasticsearch.md|73 col 36| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'that'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/authentication.md|5 col 72| [Flanksource.Spelling] Is 'elasticsearch' spelled correctly? Is it missing code formatting?
docs/apm-hub/concepts/api.md|3 col 11| [Flanksource.Spelling] Is 'Param' spelled correctly? Is it missing code formatting?
docs/apm-hub/concepts/api.md|5 col 8| [Flanksource.Spelling] Is 'param' spelled correctly? Is it missing code formatting?
docs/apm-hub/concepts/api.md|15 col 137| [Vale.Repetition] 'include' is repeated!
docs/apm-hub/overview.md|13 col 135| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simply'.
docs/apm-hub/overview.md|13 col 135| [alex.Condescending] Using 'simply' may come across as condescending.
docs/apm-hub/overview.md|13 col 135| [Flanksource.Condescending] Using 'simply' may come across as condescending.
docs/apm-hub/overview.md|26 col 5| [Flanksource.Spelling] Is 'fluentd' spelled correctly? Is it missing code formatting?
docs/apm-hub/concepts/routing.md|3 col 75| [Flanksource.Wordiness] Consider using 'all' instead of 'all of'.
docs/apm-hub/concepts/routing.md|16 col 104| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|20 col 131| [Flanksource.Spelling] Is 'idPrefix' spelled correctly? Is it missing code formatting?
docs/apm-hub/concepts/routing.md|31 col 206| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|42 col 53| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|46 col 14| [Flanksource.Adverbs] Consider removing 'really'.
docs/apm-hub/concepts/routing.md|57 col 5| [Flanksource.RacialBias] Use 'denylisting' instead of 'Blacklisting'.
docs/apm-hub/concepts/routing.md|57 col 5| [alex.Race] Consider using 'blocklisting', 'wronglisting', 'banlisting', or 'deny-listing' instead of 'Blacklisting'.
docs/apm-hub/concepts/routing.md|59 col 14| [alex.Race] Consider using 'blocklist', 'wronglist', 'banlist', or 'deny list' instead of 'blacklist'.
docs/apm-hub/concepts/routing.md|59 col 14| [Flanksource.RacialBias] Use 'denylist' instead of 'blacklist'.
docs/apm-hub/concepts/routing.md|85 col 240| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|85 col 384| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/concepts/routing.md|85 col 410| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/quick-start.md|1 col 30| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'we'll'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/quick-start.md|15 col 89| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
docs/apm-hub/quick-start.md|34 col 16| [Flanksource.DictateFeelings] Don't tell people how they feel with words like 'simple'.
docs/apm-hub/quick-start.md|34 col 16| [alex.Condescending] Using 'simple' may come across as condescending.
docs/apm-hub/quick-start.md|34 col 16| [Flanksource.Condescending] Using 'simple' may come across as condescending.
docs/apm-hub/quick-start.md|40 col 11| [Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'will'. Say '(event) happens' instead of '(event) will happen'.
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/canary-checker/comparisons/blackbox-exporter.md|3 col 136| [Flanksource.SerialComma] Use a serial comma in 'TCP, ICMP and gRPC.'.
mission-control/docs/canary-checker/database.md|48 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/canary-checker/reference/1-sql.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/getting-started.mdx|83 col 60| [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/getting-started.mdx|99 col 25| [Flanksource.Exclamation] Don't use exclamation points in text.
mission-control/docs/canary-checker/reference/_connections.mdx|144 col 18| [Flanksource.Spelling] Is 'utually' spelled correctly? Is it missing code formatting?
mission-control/docs/canary-checker/reference/1-alert-manager.mdx|11 col 180| [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-elasticsearch.mdx|7 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-elasticsearch.mdx|31 col 40| [Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
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'.
canary-checker/docs/scripting/cel.mdx|8 col 61| [Flanksource.Adverbs] Consider removing 'quickly'.
canary-checker/docs/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'.
canary-checker/docs/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'.
... (Too many findings. Dropped some findings)

Filtered Findings (0)

Annotations

Check warning on line 48 in canary-checker/docs/database.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/docs/database.md#L48

[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": "canary-checker/docs/database.md", "range": {"start": {"line": 48, "column": 123}}}, "severity": "WARNING"}

Check warning on line 3 in canary-checker/tutorials/prereqs.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/prereqs.md#L3

[Flanksource.Adverbs] Consider removing 'strictly'.
Raw output
{"message": "[Flanksource.Adverbs] Consider removing 'strictly'.", "location": {"path": "canary-checker/tutorials/prereqs.md", "range": {"start": {"line": 3, "column": 114}}}, "severity": "WARNING"}

Check failure on line 7 in canary-checker/tutorials/prereqs.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/prereqs.md#L7

[Flanksource.DictateFeelings] Don't tell people how they feel with words like 'obvious'.
Raw output
{"message": "[Flanksource.DictateFeelings] Don't tell people how they feel with words like 'obvious'.", "location": {"path": "canary-checker/tutorials/prereqs.md", "range": {"start": {"line": 7, "column": 16}}}, "severity": "ERROR"}

Check failure on line 7 in canary-checker/tutorials/prereqs.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/prereqs.md#L7

[alex.Condescending] Using 'obvious' may come across as condescending.
Raw output
{"message": "[alex.Condescending] Using 'obvious' may come across as condescending.", "location": {"path": "canary-checker/tutorials/prereqs.md", "range": {"start": {"line": 7, "column": 16}}}, "severity": "ERROR"}

Check failure on line 7 in canary-checker/tutorials/prereqs.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/prereqs.md#L7

[Flanksource.Condescending] Using 'obvious' may come across as condescending.
Raw output
{"message": "[Flanksource.Condescending] Using 'obvious' may come across as condescending.", "location": {"path": "canary-checker/tutorials/prereqs.md", "range": {"start": {"line": 7, "column": 16}}}, "severity": "ERROR"}

Check warning on line 7 in canary-checker/tutorials/prereqs.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/prereqs.md#L7

[Flanksource.Adverbs] Consider removing 'properly'.
Raw output
{"message": "[Flanksource.Adverbs] Consider removing 'properly'.", "location": {"path": "canary-checker/tutorials/prereqs.md", "range": {"start": {"line": 7, "column": 223}}}, "severity": "WARNING"}

Check warning on line 19 in canary-checker/tutorials/prereqs.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/prereqs.md#L19

[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": "canary-checker/tutorials/prereqs.md", "range": {"start": {"line": 19, "column": 13}}}, "severity": "WARNING"}

Check failure on line 52 in canary-checker/tutorials/prereqs.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/prereqs.md#L52

[Flanksource.FirstPerson] Do not use the first person (such as ' I ').
Raw output
{"message": "[Flanksource.FirstPerson] Do not use the first person (such as ' I ').", "location": {"path": "canary-checker/tutorials/prereqs.md", "range": {"start": {"line": 52, "column": 281}}}, "severity": "ERROR"}

Check warning on line 85 in canary-checker/tutorials/prereqs.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/prereqs.md#L85

[Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'You'll'. Say '(event) happens' instead of '(event) will happen'.
Raw output
{"message": "[Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'You'll'. Say '(event) happens' instead of '(event) will happen'.", "location": {"path": "canary-checker/tutorials/prereqs.md", "range": {"start": {"line": 85, "column": 1}}}, "severity": "WARNING"}

Check failure on line 1 in canary-checker/tutorials/dev-guide.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/dev-guide.md#L1

[Flanksource.Spelling] Is 'Dev' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'Dev' spelled correctly? Is it missing code formatting?", "location": {"path": "canary-checker/tutorials/dev-guide.md", "range": {"start": {"line": 1, "column": 3}}}, "severity": "ERROR"}

Check warning on line 9 in canary-checker/tutorials/dev-guide.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/dev-guide.md#L9

[Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'we'll'. Say '(event) happens' instead of '(event) will happen'.
Raw output
{"message": "[Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'we'll'. Say '(event) happens' instead of '(event) will happen'.", "location": {"path": "canary-checker/tutorials/dev-guide.md", "range": {"start": {"line": 9, "column": 15}}}, "severity": "WARNING"}

Check warning on line 22 in canary-checker/tutorials/dev-guide.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/dev-guide.md#L22

[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": "canary-checker/tutorials/dev-guide.md", "range": {"start": {"line": 22, "column": 68}}}, "severity": "WARNING"}

Check failure on line 24 in canary-checker/tutorials/dev-guide.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/dev-guide.md#L24

[Flanksource.Spelling] Is 'nvm' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'nvm' spelled correctly? Is it missing code formatting?", "location": {"path": "canary-checker/tutorials/dev-guide.md", "range": {"start": {"line": 24, "column": 12}}}, "severity": "ERROR"}

Check failure on line 25 in canary-checker/tutorials/dev-guide.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/dev-guide.md#L25

[Flanksource.Spelling] Is 'nvm' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'nvm' spelled correctly? Is it missing code formatting?", "location": {"path": "canary-checker/tutorials/dev-guide.md", "range": {"start": {"line": 25, "column": 9}}}, "severity": "ERROR"}

Check failure on line 33 in canary-checker/tutorials/dev-guide.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/dev-guide.md#L33

[Flanksource.Spelling] Is 'distro' spelled correctly? Is it missing code formatting?
Raw output
{"message": "[Flanksource.Spelling] Is 'distro' spelled correctly? Is it missing code formatting?", "location": {"path": "canary-checker/tutorials/dev-guide.md", "range": {"start": {"line": 33, "column": 25}}}, "severity": "ERROR"}

Check warning on line 37 in canary-checker/tutorials/dev-guide.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/dev-guide.md#L37

[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": "canary-checker/tutorials/dev-guide.md", "range": {"start": {"line": 37, "column": 19}}}, "severity": "WARNING"}

Check warning on line 39 in canary-checker/tutorials/dev-guide.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/dev-guide.md#L39

[Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'they'll'. Say '(event) happens' instead of '(event) will happen'.
Raw output
{"message": "[Flanksource.FutureTense] Use present tense verbs, not future tense verbs like 'they'll'. Say '(event) happens' instead of '(event) will happen'.", "location": {"path": "canary-checker/tutorials/dev-guide.md", "range": {"start": {"line": 39, "column": 74}}}, "severity": "WARNING"}

Check warning on line 70 in canary-checker/tutorials/dev-guide.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/tutorials/dev-guide.md#L70

[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": "canary-checker/tutorials/dev-guide.md", "range": {"start": {"line": 70, "column": 18}}}, "severity": "WARNING"}

Check warning on line 3 in canary-checker/docs/comparisons/blackbox-exporter.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/docs/comparisons/blackbox-exporter.md#L3

[Flanksource.SerialComma] Use a serial comma in 'TCP, ICMP and gRPC.'.
Raw output
{"message": "[Flanksource.SerialComma] Use a serial comma in 'TCP, ICMP and gRPC.'.", "location": {"path": "canary-checker/docs/comparisons/blackbox-exporter.md", "range": {"start": {"line": 3, "column": 136}}}, "severity": "WARNING"}

Check warning on line 83 in canary-checker/docs/getting-started.mdx

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/docs/getting-started.mdx#L83

[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": "canary-checker/docs/getting-started.mdx", "range": {"start": {"line": 83, "column": 60}}}, "severity": "WARNING"}

Check failure on line 99 in canary-checker/docs/getting-started.mdx

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/docs/getting-started.mdx#L99

[Flanksource.Exclamation] Don't use exclamation points in text.
Raw output
{"message": "[Flanksource.Exclamation] Don't use exclamation points in text.", "location": {"path": "canary-checker/docs/getting-started.mdx", "range": {"start": {"line": 99, "column": 25}}}, "severity": "ERROR"}

Check warning on line 9 in canary-checker/docs/reference/1-sql.mdx

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/docs/reference/1-sql.mdx#L9

[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": "canary-checker/docs/reference/1-sql.mdx", "range": {"start": {"line": 9, "column": 12}}}, "severity": "WARNING"}

Check warning on line 11 in canary-checker/docs/reference/1-alert-manager.mdx

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/docs/reference/1-alert-manager.mdx#L11

[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": "canary-checker/docs/reference/1-alert-manager.mdx", "range": {"start": {"line": 11, "column": 180}}}, "severity": "WARNING"}

Check warning on line 7 in canary-checker/docs/reference/1-elasticsearch.mdx

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/docs/reference/1-elasticsearch.mdx#L7

[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": "canary-checker/docs/reference/1-elasticsearch.mdx", "range": {"start": {"line": 7, "column": 12}}}, "severity": "WARNING"}

Check warning on line 31 in canary-checker/docs/reference/1-elasticsearch.mdx

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] canary-checker/docs/reference/1-elasticsearch.mdx#L31

[Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.
Raw output
{"message": "[Flanksource.ProfanityUnlikely] Be careful with 'executed', it's profane in some cases.", "location": {"path": "canary-checker/docs/reference/1-elasticsearch.mdx", "range": {"start": {"line": 31, "column": 40}}}, "severity": "WARNING"}