vale: prune accepted vocabulary

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>

docs/auth/add-auth-provider.md

@@ -230,7 +230,7 @@ name.
 ### Test the new provider
 
 You can `curl -i localhost:7007/api/auth/providerA/start` and which should
-provide a `302` redirect with a `Location` header. Paste the url from that
+provide a `302` redirect with a `Location` header. Paste the URL from that
 header into a web browser and you should be able to trigger the authorization
 flow.
 

docs/auth/github/provider.md

@@ -50,7 +50,7 @@ The GitHub provider is a structure with three configuration keys:
 - `clientSecret`: The client secret tied to the generated client ID.
 - `enterpriseInstanceUrl` (optional): The base URL for a GitHub Enterprise
   instance, e.g. `https://ghe.<company>.com`. Only needed for GitHub Enterprise.
-- `callbackUrl` (optional): The callback url that GitHub will use when
+- `callbackUrl` (optional): The callback URL that GitHub will use when
   initiating an OAuth flow, e.g.
   `https://your-intermediate-service.com/handler`. Only needed if Backstage is
   not the immediate receiver (e.g. one OAuth app for many backstage instances).

docs/conf/writing.md

@@ -161,7 +161,7 @@ $file: ./my-secret.txt
 
 The `$include` keyword can be used to load configuration values from an external
 file. It's able to load and parse data from `.json`, `.yml`, and `.yaml` files.
-It's also possible to include a url fragment (`#`) to point to a value at the
+It's also possible to include a URL fragment (`#`) to point to a value at the
 given path in the file, using a dot-separated list of keys.
 
 For example, the following would read `my-secret-key` from `my-secrets.json`:

docs/features/techdocs/concepts.md

@@ -18,8 +18,8 @@ GitLab, etc.) and passes the files to the generator for next steps.
 
 There are two kinds of preparers available -
 
-1. Common Git Preparer - Uses `git clone` on any repository url.
-2. Url Reader - Uses source code hosting provider's API to download files.
+1. Common Git Preparer - Uses `git clone` on any repository URL.
+2. URL Reader - Uses source code hosting provider's API to download files.
    (Faster and recommended)
 
 ### TechDocs Generator

docs/features/techdocs/using-cloud-storage.md

@@ -461,7 +461,7 @@ Since the new SDK doesn't use the old way authentication, we don't need the keys
 
 The new SDK needs the OpenStack Swift connection URL for connecting the Swift.
 So you need to add a new key called `openStackSwift.swiftUrl` and give the
-OpenStack Swift url here. Example url should look like that:
+OpenStack Swift URL here. Example URL should look like that:
 `https://example.com:6780/swift/v1`
 
 ##### That's it!

docs/integrations/gerrit/locations.md

@@ -34,9 +34,9 @@ a structure with up to six elements:
 - `baseUrl` (optional): Needed if the Gerrit instance is not reachable at
   the base of the `host` option (e.g. `https://gerrit.company.com`) set the
   address here. This is the address that you would open in a browser.
-- `cloneUrl` (optional): The base url for HTTP clones. Will default to `baseUrl` if
+- `cloneUrl` (optional): The base URL for HTTP clones. Will default to `baseUrl` if
   not set. The address used to clone a repo is the `cloneUrl` plus the repo name.
-- `gitilesBaseUrl` (optional): This is needed for creating a valid user-friendly url
+- `gitilesBaseUrl` (optional): This is needed for creating a valid user-friendly URL
   that can be used for browsing the content of the provider. If not set a default
   value will be created in the same way as the "baseUrl" option. There is no
   requirement to have Gitiles for the Backstage Gerrit integration but without it

docs/integrations/google-cloud-storage/locations.md

@@ -48,7 +48,7 @@ you can check [this documentation page][google gcs docs].
 To use this integration to import entities from a GCS bucket go to the Google
 console and browse the file you would like to import. Then copy the
 `Authenticated URL` and paste it into the text box in the `register component`
-form. This url should look like
+form. This URL should look like
 `https://storage.cloud.google.com/<bucket>/<path>/catalog-info.yaml`.
 
 [google gcs docs]: https://cloud.google.com/docs/authentication/production#auth-cloud-implicit-nodejs

docs/tutorials/using-backstage-proxy-within-plugin.md

@@ -52,7 +52,7 @@ calling `${backend-url}/api/proxy/<your-proxy-uri>`. The reason why
 `backend-url` is referenced is because the backstage backend creates and runs
 the proxy. Backstage is structured in such a way that you could run the
 backstage frontend independently of the backend. So when calling your API you
-need to prepend the backend url to your http call.
+need to prepend the backend URL to your http call.
 
 The recommended pattern for calling out to services is to wrap your calls in a
 [Utility API](../api/utility-apis.md). This section describes the steps to wrap