Address all warnings in content/master

I tried to address them everywhere but there are literally thousands.

Signed-off-by: Nic Cope <[email protected]>

Author: negz

content/master/cli/_index.md

@@ -41,7 +41,7 @@ https://releases.crossplane.io/stable/current/bin
 
 {{<hint "important" >}}
 <!-- vale write-good.Passive = NO -->
-The CLI is named `crank` in the release repository. Download this file.
+The release repository names the CLI `crank`. Download this file.
 <!-- vale write-good.Passive = YES -->
 
 The `crossplane` binary is the Kubernetes Crossplane pod image.

content/master/cli/command-reference.md

@@ -24,7 +24,11 @@ The following flags are available for all commands.
 
 {{< /table >}}
 
+<!-- vale Google.Headings = NO -->
+<!-- vale Microsoft.Headings = NO -->
 ## version
+<!-- vale Google.Headings = YES -->
+<!-- vale Microsoft.Headings = YES -->
 
 The `crossplane version` command returns the version of Crossplane CLI
 and the control plane.
@@ -35,7 +39,9 @@ Client Version: v1.17.0
 Server Version: v1.17.0
 ```
 
+<!-- vale Google.Headings = NO -->
 ## render
+<!-- vale Google.Headings = YES -->
 
 The `crossplane render` command previews the output of a 
 [composite resource]({{<ref "../composition/composite-resources">}}) after applying
@@ -167,21 +173,25 @@ spec:
 
 The schema of the resource isn't validated and may contain any data.
 
-### Mock Extra Resources
+### Mock extra resources
 
 Extra Resources allow a Composition to request Crossplane Objects on the cluster that aren't
 part of the Composition. The `--extra-resources` option points at a directory containing
 YAML manifests of resources to mock. Use Extra Resources in combination with a function like
 [function-extra-resources](https://github.com/crossplane-contrib/function-extra-resources) or the 
 built-in support in [function-go-templating](https://github.com/crossplane-contrib/function-go-templating?tab=readme-ov-file#extraresources).
 
+<!-- vale Google.Headings = NO -->
 ## xpkg
+<!-- vale Google.Headings = YES -->
 
 The `crossplane xpkg` commands create, install and update Crossplane
-[packages]({{<ref "../packages/configurations">}}) as well as enable authentication
+[packages]({{<ref "../packages/configurations">}}) and enable authentication
 and publishing of Crossplane packages to a Crossplane package registry.
 
+<!-- vale Google.Headings = NO -->
 ### xpkg build
+<!-- vale Google.Headings = YES -->
 
 Using `crossplane xpkg build` provides automation and simplification to build
 Crossplane packages.  
@@ -243,7 +253,7 @@ Include YAML files demonstrating how to use the package with `--examples-root`.
 #### Include a runtime image
 
 Functions and Providers require YAML files describing their dependencies and 
-settings as well as a container image for their runtime.
+settings and a container image for their runtime.
 
 Using `--embed-runtime-image-name` runs a specified image and 
 includes the image inside the function or provider package.
@@ -258,7 +268,9 @@ Use `docker pull` to download a missing image.
 The `--embed-runtime-image-tarball` flag includes a local OCI image tarball 
 inside the function or provider package.
 
+<!-- vale Google.Headings = NO -->
 ### xpkg init
+<!-- vale Google.Headings = YES -->
 
 The `crossplane xpkg init` command populates the current directory with 
 files to build a package. 
@@ -279,14 +291,18 @@ The `<template>` value may be one of four well known templates:
 Instead of a well known template the `<template>` value can be a git repository 
 URL.
 
+<!-- vale Google.Headings = NO -->
 #### NOTES.txt
+<!-- vale Google.Headings = YES -->
 
 If the template repository contains a `NOTES.txt` file in its root directory,
 the `crossplane xpkg init` command prints the contents of the file to the
 terminal after populating the directory with the template files. This can be
 useful for providing information about the template.
 
+<!-- vale Google.Headings = NO -->
 #### init.sh
+<!-- vale Google.Headings = YES -->
 
 If the template repository contains an `init.sh` file in its root directory, the
 `crossplane xpkg init` command starts a dialog after populating the
@@ -305,7 +321,9 @@ personalize the template.
 {{< /table >}}
 
 
+<!-- vale Google.Headings = NO -->
 ### xpkg install
+<!-- vale Google.Headings = YES -->
 
 Download and install packages into Crossplane with  `crossplane xpkg install`.
 
@@ -375,7 +393,9 @@ Read more about
 [package revisions]({{< ref "../packages/configurations#configuration-revisions" >}}) 
 in the package documentation. 
 
+<!-- vale Google.Headings = NO -->
 ### xpkg login
+<!-- vale Google.Headings = YES -->
 
 Use `xpkg login` to authenticate to registries that host Crossplane packages.
 
@@ -430,7 +450,9 @@ Authenticate to a registered organization in the Upbound Marketplace with the
 For example, 
 `crossplane xpkg login --account=Upbound --username=my-user --password -`.
 
+<!-- vale Google.Headings = NO -->
 ### xpkg logout
+<!-- vale Google.Headings = YES -->
 
 Use `crossplane xpkg logout` to invalidate the current `crossplane xpkg login` 
 session.
@@ -440,7 +462,9 @@ Using `crossplane xpkg logout` removes the `session` from the
 `~/.crossplane/config.json` file, but doesn't delete the configuration file.
 {{< /hint >}}
 
+<!-- vale Google.Headings = NO -->
 ### xpkg push
+<!-- vale Google.Headings = YES -->
 
 Push a Crossplane package file to a package registry. 
 
@@ -478,7 +502,9 @@ DockerHub organization `crossplane-docs/my-package:v0.14.0` use:
 | `-f`         | `--package-files=PATH` | A comma-separated list of xpkg files to push. |
 {{< /table >}}
 
+<!-- vale Google.Headings = NO -->
 ### xpkg update
+<!-- vale Google.Headings = YES -->
 
 The `crossplane xpkg update` command downloads and updates an existing package.
 
@@ -499,7 +525,9 @@ For example, to update to the latest version of the
 `crossplane xpkg update provider xpkg.crossplane.io/crossplane-contrib/provider-aws-s3:v1.21.1`
 
 
+<!-- vale Google.Headings = NO -->
 ## beta
+<!-- vale Google.Headings = YES -->
 
 Crossplane `beta` commands are experimental. These commands may change the 
 flags, options or outputs in future releases. 
@@ -508,7 +536,9 @@ Crossplane maintainers may promote or remove commands under `beta` in future
 releases.
 
 
+<!-- vale Google.Headings = NO -->
 ### beta convert
+<!-- vale Google.Headings = YES -->
 
 As Crossplane evolves, its APIs and resources may change. To help with the 
 migration to the new APIs and resources, the `crossplane beta convert` command
@@ -547,7 +577,9 @@ By default the function name is "function-patch-and-transform."
 {{< /table >}}
 
 
+<!-- vale Google.Headings = NO -->
 ### beta top
+<!-- vale Google.Headings = YES -->
 
 The command `crossplane beta top` shows CPU and memory usage of Crossplane
 related pods. 
@@ -591,7 +623,9 @@ running the `top` command may produce an error, for example,
 `crossplane: error: error adding metrics to pod, check if metrics-server is running or wait until metrics are available for the pod: the server is currently unable to handle the request (get pods.metrics.k8s.io crossplane-contrib-provider-helm-b4cc4c2c8db3-6d787f9686-qzmz2)`
 
 
+<!-- vale Google.Headings = NO -->
 ### beta trace
+<!-- vale Google.Headings = YES -->
 
 Use the `crossplane beta trace` command to display a visual relationship of
 Crossplane objects. The `trace` command supports XRs, compositions, 
@@ -826,7 +860,9 @@ Configuration/platform-ref-aws                             v0.9.0    True
 # Removed for brevity
 ```
 
+<!-- vale Google.Headings = NO -->
 ### beta validate
+<!-- vale Google.Headings = YES -->
 
 The `crossplane beta validate` command validates 
 [compositions]({{<ref "../composition/compositions">}}) against provider or XRD 
@@ -953,7 +989,9 @@ crossplane render xr.yaml composition.yaml function.yaml --include-full-xr | cro
 Total 5 resources: 0 missing schemas, 4 success cases, 1 failure cases
 ```
 
+<!-- vale Google.Headings = NO -->
 #### Validate Common Expression Language rules
+<!-- vale Google.Headings = YES -->
 
 XRDs can define [validation rules](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation-rules) expressed in the Common Expression Language 
 ([CEL](https://kubernetes.io/docs/reference/using-api/cel/)).

content/master/composition/composite-resource-definitions.md

@@ -30,7 +30,11 @@ Crossplane XRDs are like
 XRDs require fewer fields and add options related to Crossplane, like connection
 secrets. 
 
+<!-- vale Google.Headings = NO -->
+<!-- vale Microsoft.Headings = NO -->
 ## Creating a CompositeResourceDefinition
+<!-- vale Google.Headings = YES -->
+<!-- vale Microsoft.Headings = YES -->
 
 Creating a CompositeResourceDefinition consists of:
 * [Defining a custom API group](#xrd-groups).
@@ -88,7 +92,11 @@ recreate the XRD to change the
 {{<hover label="xrd1" line="7">}}names{{</hover>}}.
 {{</hint >}}
 
+<!-- vale Google.Headings = NO -->
+<!-- vale Microsoft.Headings = NO -->
 ### XRD groups
+<!-- vale Google.Headings = YES -->
+<!-- vale Microsoft.Headings = YES -->
 
 Groups define a collection of related API endpoints. The `group` can be any
 value, but common convention is to map to a fully qualified domain name.
@@ -98,7 +106,11 @@ Many XRDs may use the same `group` to create a logical collection of APIs.
 <!-- vale write-good.Weasel = YES -->
 For example a `database` group may have a `relational` and `nosql` kinds. 
 
+<!-- vale Google.Headings = NO -->
+<!-- vale Microsoft.Headings = NO -->
 ### XRD names
+<!-- vale Google.Headings = YES -->
+<!-- vale Microsoft.Headings = YES -->
 
 The `names` field defines how to refer to this specific XRD.  
 The required name fields are: 
@@ -137,7 +149,11 @@ spec:
 ```
 {{</hint >}}
 
+<!-- vale Google.Headings = NO -->
+<!-- vale Microsoft.Headings = NO -->
 ### XRD versions
+<!-- vale Google.Headings = YES -->
+<!-- vale Microsoft.Headings = YES -->
 
 <!-- vale gitlab.SentenceLength = NO -->
 The XRD `version` is like the 
@@ -567,7 +583,11 @@ spec:
   # Removed for brevity
 ```
 
+<!-- vale Google.Headings = NO -->
+<!-- vale Microsoft.Headings = NO -->
 ## Verify a CompositeResourceDefinition
+<!-- vale Google.Headings = YES -->
+<!-- vale Microsoft.Headings = YES -->
 
 Verify an XRD with `kubectl get compositeresourcedefinition` or the short form, 
 {{<hover label="getxrd" line="1">}}kubectl get xrd{{</hover>}}.
@@ -581,7 +601,11 @@ xdatabases.custom-api.example.org   True          True      22m
 The `ESTABLISHED` field indicates Crossplane installed the Kubernetes custom
 resource definition for this XRD.
 
+<!-- vale Google.Headings = NO -->
+<!-- vale Microsoft.Headings = NO -->
 ### XRD conditions
+<!-- vale Google.Headings = YES -->
+<!-- vale Microsoft.Headings = YES -->
 Crossplane uses a standard set of `Conditions` for XRDs.  
 View the conditions of a XRD under their `Status` with 
 `kubectl describe xrd`. 

content/master/composition/composite-resources.md

@@ -319,15 +319,17 @@ Spec:
 
 ### Composite resource conditions
 
+<!-- vale Google.Colons = NO -->
 A composite resource has two status conditions: Synced and Ready.
+<!-- vale Google.Colons = YES -->
 
 Crossplane sets the Synced status condition to True when it's able to
 successfully reconcile the composite resource. If Crossplane can't reconcile the
-composite resource it'll report an error in the Synced condition.
+composite resource it reports an error in the Synced condition.
 
 Crossplane sets the Ready status condition to True when the composite resource's
-composition function pipeline reports that all of its composed resources are
-ready. If a composed resource isn't ready Crossplane will report it in the
+composition function pipeline reports that all its composed resources are
+ready. If a composed resource isn't ready Crossplane reports it in the
 Ready condition.
 
 ## Composite resource labels