Update v.jsonnet for VM and VMware

docs/sources/review/lint-prose/rules.md

@@ -2,7 +2,7 @@
 date: "2024-06-25"
 description: A description of every Grafana Labs prose linting rule.
 menuTitle: Rules
-review_date: "2024-09-17"
+review_date: "2024-09-19"
 title: Vale rules
 ---
 
@@ -809,6 +809,7 @@ _`<CURRENT TEXT>`_ was matched by one or more of the following regular expressio
 - `Thanos'`
 - `Velero's`
 - `Vite's`
+- `VMware's`
 - `WildFly's`
 - `windows_exporter's`
 - `Zipkin's`
@@ -985,6 +986,8 @@ Use _`<REPLACEMENT TEXT>`_ instead of _`<CURRENT TEXT>`_.
 | `Grafana AI observability`                                        | `Grafana AI Observability` |
 | `HTTPs`                                                           | `HTTPS`                    |
 | `Once`                                                            | `After`                    |
+| `VMWare`                                                          | `VMware`                   |
+| `Vmware`                                                          | `VMware`                   |
 | `[Ww]orld [Ww]ide [Ww]eb`                                         | `web`                      |
 | `[cC]entos`                                                       | `CentOS`                   |
 | `\b(?:[aA]daptive metrics\|adaptive Metrics)\b`                   | `Adaptive Metrics`         |
@@ -1053,6 +1056,7 @@ Use _`<REPLACEMENT TEXT>`_ instead of _`<CURRENT TEXT>`_.
 | `un(?:check\|select)`                                             | `clear`                    |
 | `url`                                                             | `URL`                      |
 | `urls`                                                            | `URLs`                     |
+| `vmware`                                                          | `VMware`                   |
 | `vs\.`                                                            | `versus`                   |
 | `whitelist`                                                       | `allowlist`                |
 | `whitelisted`                                                     | `allowlisted`              |

vale/Grafana/Headings.yml

@@ -71,6 +71,7 @@
   - "Thanos"
   - "Velero"
   - "Vite"
+  - "VMware"
   - "WildFly"
   - "windows_exporter"
   - "Zipkin"

vale/Grafana/ProductPossessives.yml

@@ -71,6 +71,7 @@
   - "Thanos'"
   - "Velero's"
   - "Vite's"
+  - "VMware's"
   - "WildFly's"
   - "windows_exporter's"
   - "Zipkin's"

vale/Grafana/WordList.yml

@@ -26,6 +26,8 @@
   "Grafana AI observability": "Grafana AI Observability"
   "HTTPs": "HTTPS"
   "Once": "After"
+  "VMWare": "VMware"
+  "Vmware": "VMware"
   "[Ww]orld [Ww]ide [Ww]eb": "web"
   "[cC]entos": "CentOS"
   "\\b(?:[aA]daptive metrics|adaptive Metrics)\\b": "Adaptive Metrics"
@@ -94,6 +96,7 @@
   "un(?:check|select)": "clear"
   "url": "URL"
   "urls": "URLs"
+  "vmware": "VMware"
   "vs\\.": "versus"
   "whitelist": "allowlist"
   "whitelisted": "allowlisted"

vale/dictionaries/en_US-grafana.dic

@@ -1,4 +1,4 @@
-297
+299
 ACL/S po:noun
 AI Observability/ po:noun
 Adaptive Metrics/ po:noun
@@ -277,6 +277,8 @@ Velero/ po:noun
 versus/ po:preposition
 viewport/S po:noun
 Vite/ po:noun
+VM/S po:noun
+VMware/ po:noun
 VPC/S po:noun
 VU/S po:noun
 VUH/S po:noun

vale/dictionary/v.jsonnet

@@ -4,6 +4,8 @@ local word = import './word.jsonnet';
   word.new('versus', '', 'preposition') { description: 'against (https://en.wiktionary.org/wiki/versus)', swaps: { 'vs\\.': 'versus' } },
   word.new('viewport', 'S', 'noun') { description: 'A viewport is a polygon viewing region in computer graphics (https://en.wikipedia.org/wiki/Viewport)' },
   word.new('Vite', '', 'noun') { description: 'Next Generation Frontend Tooling (https://vitejs.dev/)', product: true },
+  word.new('VM', 'S', 'noun') { description: 'Virtual Machine' },
+  word.new('VMware', '', 'noun') { description: 'VMware LLC is an American cloud computing and virtualization technology company.', product: true, swaps: { vmware: 'VMware', Vmware: 'VMware', VMWare: 'VMware' } },
   word.new('VPC', 'S', 'noun') { abbreviation: true, elaboration: 'virtual private cloud', established_abbreviation: true },
   word.new('VU', 'S', 'noun') { abbreviation: true, elaboration: 'virtual user' },
   word.new('VUH', 'S', 'noun') { abbreviation: true, elaboration: 'virtual user hour' },

vale/fixtures/Grafana/Admin/testinvalid.golden

@@ -1 +1 @@
-testinvalid.md:3:3:Grafana.Admin:Use administrator instead of admin unless it's the name of the UI label like in the Grafana 'Admin' role. 
+testinvalid.md:3:3:Grafana.Admin:Use 'administrator' instead of 'admin' unless it's the name of the UI label like in the Grafana 'Admin' role. 

vale/fixtures/Grafana/Agentless/testinvalid.golden

@@ -1,2 +1,2 @@
-testinvalid.md:3:3:Grafana.Agentless:Grafana Agent has been replaced by Grafana Alloy, so you shouldn't use agent-based terminology. If you're talking about why and how to send signals directly from an application to Grafana Cloud, prefer no-collector to agentless. This is consistent with [OTel documentation](https://opentelemetry.io/docs/collector/deployment/no-collector/). 
-testinvalid.md:4:3:Grafana.Agentless:Grafana Agent has been replaced by Grafana Alloy, so you shouldn't use agent-based terminology. If you're talking about why and how to send signals directly from an application to Grafana Cloud, prefer no-collector to agentless. This is consistent with [OTel documentation](https://opentelemetry.io/docs/collector/deployment/no-collector/). 
+testinvalid.md:3:3:Grafana.Agentless:Use 'no-collector' instead of 'agentless'. Grafana Agent has been replaced by Grafana Alloy, so you shouldn't use agent-based terminology. If you're talking about why and how to send signals directly from an application to Grafana Cloud, prefer no-collector to agentless. This is consistent with [OTel documentation](https://opentelemetry.io/docs/collector/deployment/no-collector/). 
+testinvalid.md:4:3:Grafana.Agentless:Use 'no-collector' instead of 'agentless'. Grafana Agent has been replaced by Grafana Alloy, so you shouldn't use agent-based terminology. If you're talking about why and how to send signals directly from an application to Grafana Cloud, prefer no-collector to agentless. This is consistent with [OTel documentation](https://opentelemetry.io/docs/collector/deployment/no-collector/). 

vale/fixtures/Grafana/DropDown/testinvalid.golden

@@ -1,2 +1,2 @@
-testinvalid.md:3:3:Grafana.DropDown:Use _drop-down_ rather than _dropdown_ or _drop down_. Use drop-down as a modifier rather than as a standalone noun. For example: _drop-down menu_. 
-testinvalid.md:4:3:Grafana.DropDown:Use _drop-down_ rather than _dropdown_ or _drop down_. Use drop-down as a modifier rather than as a standalone noun. For example: _drop-down menu_. 
+testinvalid.md:3:3:Grafana.DropDown:Use 'drop-down' instead of 'dropdown'. Use drop-down as a modifier rather than as a standalone noun. For example: _drop-down menu_. 
+testinvalid.md:4:3:Grafana.DropDown:Use 'drop-down' instead of 'drop down'. Use drop-down as a modifier rather than as a standalone noun. For example: _drop-down menu_. 

vale/fixtures/Grafana/Quickstart/testinvalid.golden

@@ -1 +1 @@
-testinvalid.md:3:3:Grafana.Quickstart:Use the compound adjective without a hyphen whether the noun is implied or explicit. For example, you can use _quickstart guide_ or just _quickstart_.
+testinvalid.md:3:3:Grafana.Quickstart:Use the compound adjective 'quickstart' without a hyphen instead of 'quick start' whether the noun is implied or explicit. For example, you can use _quickstart guide_ or just _quickstart_.

vale/fixtures/Grafana/Shortcodes/testinvalid.golden

@@ -1,5 +1,5 @@
-testinvalid.md:3:3:Grafana.Shortcodes:Prefer `{{< admonition type="<TYPE>" >}}`. It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode. 
-testinvalid.md:4:3:Grafana.Shortcodes:Prefer `{{< admonition type="<TYPE>" >}}`. It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode. 
-testinvalid.md:5:3:Grafana.Shortcodes:Prefer `{{< admonition type="<TYPE>" >}}`. It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode. 
-testinvalid.md:6:3:Grafana.Shortcodes:Prefer `{{< admonition type="<TYPE>" >}}`. It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode. 
-testinvalid.md:7:3:Grafana.Shortcodes:Prefer `{{< admonition type="<TYPE>" >}}`. It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode. 
+testinvalid.md:3:3:Grafana.Shortcodes:Prefer `{{<` and `>}}` instead of `{{%!`(string={{% admonition type="caution" %}}) and `%!}(string=)}` It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode. 
+testinvalid.md:4:3:Grafana.Shortcodes:Prefer `{{<` and `>}}` instead of `{{%!`(string={{% admonition type="note" %}}) and `%!}(string=)}` It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode. 
+testinvalid.md:5:3:Grafana.Shortcodes:Prefer `{{<` and `>}}` instead of `{{%!`(string={{% admonition type="tip" %}}) and `%!}(string=)}` It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode. 
+testinvalid.md:6:3:Grafana.Shortcodes:Prefer `{{<` and `>}}` instead of `{{%!`(string={{% admonition type="warn" %}}) and `%!}(string=)}` It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode. 
+testinvalid.md:7:3:Grafana.Shortcodes:Prefer `{{<` and `>}}` instead of `{{%!`(string={{% /admonition %}}) and `%!}(string=)}` It has the most consistent semantics. The percent syntax is used for special behavior that isn't required with this shortcode.