From d012993619cecef2ba52264afb2e9d2dcaf1931d Mon Sep 17 00:00:00 2001 From: Kristin Martin Date: Tue, 20 Oct 2026 01:09:32 +0000 Subject: [PATCH] Fix the typos found while adding meta descriptions The unambiguous half of docs-tracking#370: missing and doubled words, two misspellings, IPv6 casing, UK spellings, and a mangled URL in sample output. Also five of the same typos on pages #370 does not list, since fixing one and leaving its twin two files away reads as carelessness. Left the `ECTO_IPV6` environment variable alone. Leaves #370's judgment calls: the self-contradictions, the 2023 sample output, and the claims that want someone else's sign-off. --- about/pricing.mdx | 2 +- app-guides/6pndemochat.mdx | 2 +- app-guides/minio.mdx | 2 +- app-guides/multiple-processes.mdx | 2 +- app-guides/nats-cluster.mdx | 2 +- getting-started/launch-demo.mdx | 2 +- laravel/index.mdx | 2 +- launch/create.mdx | 2 +- machines/runtime-environment.mdx | 2 +- monitoring/logging-overview.mdx | 2 +- monitoring/logs-api-options.mdx | 2 +- networking/request-headers.mdx | 2 +- networking/udp-and-tcp.mdx | 2 +- security/openid-connect.mdx | 10 +++++----- 14 files changed, 18 insertions(+), 18 deletions(-) diff --git a/about/pricing.mdx b/about/pricing.mdx index 9dd37c838d..8bb1ba73fb 100644 --- a/about/pricing.mdx +++ b/about/pricing.mdx @@ -130,7 +130,7 @@ For stopped Machines we charge only for the root file system (rootfs) needed for ### Machine reservation blocks You'll get a 40% discount when you reserve a block of compute time, either for `performance` Machines or `shared` Machines, in a specific region. -Reservations apply to any number of Machines of the specified CPU class, in the specified region, in any of your organisation's apps. +Reservations apply to any number of Machines of the specified CPU class, in the specified region, in any of your organization's apps. The available reservation sizes are: diff --git a/app-guides/6pndemochat.mdx b/app-guides/6pndemochat.mdx index 06f9a41a2e..c857b89f06 100644 --- a/app-guides/6pndemochat.mdx +++ b/app-guides/6pndemochat.mdx @@ -71,7 +71,7 @@ let natsapphost=process.env.NATSAPPHOST const nc = NATS.connect(natsapphost+".internal"); ``` -The combination of an app name and `.internal` in 6PN networking resolves to the IPV6 addresses of the first instance of all instances if that app currently running. So, if we set NATSAPP to `myclusterapp` then scaling and adding nodes to `myclusterapp` would automatically be reflected in `myclusterapp.internal`. 6PN has a number of `.internal` addresses an app can query which you can read about in the [6PN documentation](/networking/services#internal-addresses). +The combination of an app name and `.internal` in 6PN networking resolves to the IPv6 addresses of the first instance of all instances if that app currently running. So, if we set NATSAPP to `myclusterapp` then scaling and adding nodes to `myclusterapp` would automatically be reflected in `myclusterapp.internal`. 6PN has a number of `.internal` addresses an app can query which you can read about in the [6PN documentation](/networking/services#internal-addresses). Once the chat server has connected to the NATS cluster, it subscribes to a topic `msg` and any message written to `msg` will be broadcast to all web socket clients that are connected. If any of those web socket clients sends a message to the chat server, then it will publish that message to the `msg` topic on the NATs cluster. It doesn't even try to echo it locally, relying on the NATS cluster to publish to subscribers. diff --git a/app-guides/minio.mdx b/app-guides/minio.mdx index b6559bc2ba..f6351016d5 100644 --- a/app-guides/minio.mdx +++ b/app-guides/minio.mdx @@ -56,7 +56,7 @@ Your app is ready! Deploy with `flyctl deploy` ## (Un)configure networking -There's no need for this app to be accessible from the public internet, if you run your object storage within the same [Fly IPV6 private network](/networking/private-networking) as the app(s) that want to connect to it. +There's no need for this app to be accessible from the public internet, if you run your object storage within the same [Fly IPv6 private network](/networking/private-networking) as the app(s) that want to connect to it. Delete the `[http_service]` block in `fly.toml`. Now the Fly proxy won't pass any requests to the app from outside your private network. diff --git a/app-guides/multiple-processes.mdx b/app-guides/multiple-processes.mdx index bd06587142..6b8e114645 100644 --- a/app-guides/multiple-processes.mdx +++ b/app-guides/multiple-processes.mdx @@ -203,7 +203,7 @@ root@30952b25:/# overmind connect foo # (clouds part, screen fills with foo's terminal) ``` -If you're not a `tmux` person, `ctr-b d` detaches you from that window. +If you're not a `tmux` person, `ctrl-b d` detaches you from that window. ### There are so many other process managers diff --git a/app-guides/nats-cluster.mdx b/app-guides/nats-cluster.mdx index f24a61de86..00833108b5 100644 --- a/app-guides/nats-cluster.mdx +++ b/app-guides/nats-cluster.mdx @@ -46,7 +46,7 @@ Then run `flyctl logs` and you'll see the virtual machines discover each other. ## Testing the cluster -While the cluster is only accessible from inside the Fly network, you can use Fly's [Wireguard support](/networking/private-networking) to create a VPN into your Fly organisation and private network. +While the cluster is only accessible from inside the Fly network, you can use Fly's [Wireguard support](/networking/private-networking) to create a VPN into your Fly organization and private network. Then you can use tools such as [natscli](https://github.com/nats-io/natscli) to subscribe to topics, publish messages to topics and perform various tests on your NATS cluster. Install the tool first. diff --git a/getting-started/launch-demo.mdx b/getting-started/launch-demo.mdx index 48e22ec5c0..f340d6c90a 100644 --- a/getting-started/launch-demo.mdx +++ b/getting-started/launch-demo.mdx @@ -135,7 +135,7 @@ For fun, add `/` to `fly apps open` and your name will be appended to fly apps open /fred ``` ```out out -opening https:http://hellofly.fly.dev/fred ... +opening https://hellofly.fly.dev/fred ... ``` diff --git a/laravel/index.mdx b/laravel/index.mdx index f3deb07ce5..4d55abfcff 100644 --- a/laravel/index.mdx +++ b/laravel/index.mdx @@ -72,7 +72,7 @@ Once you accept the configuration, this would proceed with **adding [default sec 3. [Dockerfile](https://github.com/fly-apps/dockerfile-laravel/blob/main/resources/views/dockerfile.blade.php) - Used to build a container image that is run in fly 4. [.dockerignore](https://github.com/fly-apps/dockerfile-laravel/blob/main/resources/views/fly/dockerignore.blade.php) - Used to ensure certain files don’t make its way into your image -With the configuration files and extenstion apps in place, an image is built for your app using your project and the Dockerfile generated for it. This image is then finally used to deploy your app. +With the configuration files and extension apps in place, an image is built for your app using your project and the Dockerfile generated for it. This image is then finally used to deploy your app. #### Success! You should be able to visit `https://your-app-name.fly.dev` and see the Laravel demo home page. diff --git a/launch/create.mdx b/launch/create.mdx index ac7caee075..e56057683f 100644 --- a/launch/create.mdx +++ b/launch/create.mdx @@ -43,7 +43,7 @@ The components of a successful launch, ready for the first deployment: * A way to get a Docker image that we can use to get your app running on a Machine. Usually that's a Dockerfile, which `fly launch` can generate for you. * A `fly.toml` file, created by `fly launch` or provided by you, for your app's Fly.io-specific [configuration](/reference/configuration). -* Optional resources such as [public IP addresses](/networking/services), [app secrets](/apps/secrets), and [databases and storage](/database-storage-guides) from Fly.io or extenstion partners. +* Optional resources such as [public IP addresses](/networking/services), [app secrets](/apps/secrets), and [databases and storage](/database-storage-guides) from Fly.io or extension partners. ## Framework launch scanners diff --git a/machines/runtime-environment.mdx b/machines/runtime-environment.mdx index db96ab287d..2815c3ccbc 100644 --- a/machines/runtime-environment.mdx +++ b/machines/runtime-environment.mdx @@ -27,7 +27,7 @@ Environment variables make several kinds of information available within a Machi Not to be confused with the [HTTP header](/networking/request-headers#fly-region) `Fly-Region`, which is where the connection was accepted from. ### `FLY_PUBLIC_IP` -**IPV6 public IP**: The full public outbound IPV6 address for this Machine. Read more in the [Network Services](/networking/services#outbound-ip-addresses) section. +**IPv6 public IP**: The full public outbound IPv6 address for this Machine. Read more in the [Network Services](/networking/services#outbound-ip-addresses) section. ### `FLY_IMAGE_REF` **Docker image reference**: The name of the Docker image used to create the Machine. `registry.fly.io/my-app-name:deployment-01H9RK9EYO9PGNBYAKGXSHV0PH` is an example of the Docker Image Reference's format. diff --git a/monitoring/logging-overview.mdx b/monitoring/logging-overview.mdx index 021915c673..8004d23793 100644 --- a/monitoring/logging-overview.mdx +++ b/monitoring/logging-overview.mdx @@ -12,7 +12,7 @@ Outside of the Machine, on the host, we take that output and send it to [Vector] A proxy sits in front of NATS, to ensure you only see your own logs, and you can hook into NATS via this proxy to get your logs. -Vector can act as a NATS client, read the logs, and ship them somewhere. An example of this our Fly Log Shipper app. +Vector can act as a NATS client, read the logs, and ship them somewhere. An example of this is our Fly Log Shipper app. ## Live tail logs diff --git a/monitoring/logs-api-options.mdx b/monitoring/logs-api-options.mdx index ead7fe11d7..43471bfc50 100644 --- a/monitoring/logs-api-options.mdx +++ b/monitoring/logs-api-options.mdx @@ -73,7 +73,7 @@ This gives you structured JSON log messages in real time. - You’ll need to handle reconnections: if the network drops or the proxy restarts, your subscriber needs to reconnect and resume without losing messages. - You’ll need to handle backpressure: if your app can’t process logs fast enough, messages might pile up and get dropped. Design your consumer to either keep up or fail gracefully. - If you want to dedupe across subscribers, use NATS queue groups. -- NATS only streams logs from starting from the moment you connect. You won’t get any history unless you’ve been subscribed the whole time. +- NATS only streams logs starting from the moment you connect. You won’t get any history unless you’ve been subscribed the whole time. For more details on connecting to Fly’s NATS log stream (authentication, subject patterns, example clients), head over to the [Observability for User Apps](/blueprints/observability-for-user-apps#streaming-fly-app-logs-to-your-end-users) guide. diff --git a/networking/request-headers.mdx b/networking/request-headers.mdx index 6b4c20f3bb..4ec84847d2 100644 --- a/networking/request-headers.mdx +++ b/networking/request-headers.mdx @@ -28,7 +28,7 @@ Not to be confused with the [environment variable](/machines/runtime-environment **Client and Proxy List**: A comma separated list of IP addresses including the address of the client that originated the request and the addresses of the proxy servers the request passed through. For example, "77.97.0.98, 77.83.142.33" contains the client and the one proxy it passed through. On the Fly.io platform, the last address (rightmost) in this list will be a shared or dedicated IP address assigned to your app. -This header must be treated with caution to avoid spoofing attempts. Follow the directives in the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) for `X-Forwarded-For` to learn how parse the header safely. If you aren't using another reverse proxy in front of the Fly.io platform, the [`Fly-Client-IP` header](#fly-client-ip) might be a better choice to get client IP addresses. +This header must be treated with caution to avoid spoofing attempts. Follow the directives in the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For) for `X-Forwarded-For` to learn how to parse the header safely. If you aren't using another reverse proxy in front of the Fly.io platform, the [`Fly-Client-IP` header](#fly-client-ip) might be a better choice to get client IP addresses. ### `X-Forwarded-Proto` diff --git a/networking/udp-and-tcp.mdx b/networking/udp-and-tcp.mdx index 88d50d1b49..368166d2c3 100644 --- a/networking/udp-and-tcp.mdx +++ b/networking/udp-and-tcp.mdx @@ -6,7 +6,7 @@ source_url: https://fly.io/docs/networking/udp-and-tcp/ You can run any containerized app on our platform, regardless of what protocols it talks over, including apps that rely on UDP in addition to TCP. This guide walks you through how to set up your UDP app on Fly.io. -Before getting started, here's the summary of important points about using up UDP on Fly.io (that we'll expand on below): +Before getting started, here's the summary of important points about using UDP on Fly.io (that we'll expand on below): * You need a dedicated IPv4 address. You can't use a shared IPv4 address or an IPv6 address for UDP. We support public IPv6 and shared IPv4 for TCP. diff --git a/security/openid-connect.mdx b/security/openid-connect.mdx index e42c9a797f..0a6bc63e25 100644 --- a/security/openid-connect.mdx +++ b/security/openid-connect.mdx @@ -27,12 +27,12 @@ Every request to the token endpoint generates a unique Json Web Token (JWT). Whe { "app_id": "11111111", "app_name": "example-app", - "aud": "https://fly.io/exmaple-org", + "aud": "https://fly.io/example-org", "exp": 1712099653, "iat": 1712099053, "image": "docker-hub-mirror.fly.io/you/image:latest", "image_digest": "sha256:2c1cdaded1b3820020c9dc9fdd1d6e798d6f6ca36861bb6ae64019fad6be9ee3", - "iss": "https://oidc.fly.io/exmaple-org", + "iss": "https://oidc.fly.io/example-org", "jti": "93ca09e1-70e0-477b-a260-1d8fcd4ef4f4", "machine_id": "148e21ea7e46e8", "machine_name": "example-machine", @@ -57,7 +57,7 @@ curl --unix-socket /.fly/api -X POST "http://localhost/v1/tokens/oidc" --data '{ ## OpenID Connect Trust Policies in AWS -You can leverage the trust policy of an IAM role to restrict which Machines in your organisation can assume a role in AWS. For example the following policy would only allow Machines in the app `foo-bar` within your org to assume the role it’s attached to. +You can leverage the trust policy of an IAM role to restrict which Machines in your organization can assume a role in AWS. For example the following policy would only allow Machines in the app `foo-bar` within your org to assume the role it’s attached to. ```json { @@ -87,7 +87,7 @@ You can leverage the trust policy of an IAM role to restrict which Machines in y To read from an S3 bucket using a Fly Machine you'll first need to set up a trust between AWS and Fly.io by creating an OIDC provider in AWS and then attaching a trust policy to the role policy your Machine will assume. If you've already packaged up your app in a Dockerfile, then you can follow these steps to read from an S3 bucket: 1. Create a Fly.io app by running `fly launch` in the same directory as your Dockerfile. -1. Find the slug for the organisation you want to launch your app in. +1. Find the slug for the organization you want to launch your app in. ```bash fly orgs list @@ -111,7 +111,7 @@ To read from an S3 bucket using a Fly Machine you'll first need to set up a trus AWS_ROLE_ARN = "arn:aws:iam:::role/" ``` -1. Deploy your app and let the AWS SDK will do the rest. +1. Deploy your app and let the AWS SDK do the rest. ```bash fly deploy