diff --git a/blueprints/cell-based.html.md b/blueprints/cell-based.html.md index ab99fbb04c..ee0ea8b274 100644 --- a/blueprints/cell-based.html.md +++ b/blueprints/cell-based.html.md @@ -246,7 +246,7 @@ As mentioned above, backups are crucial. Items to explore: supports failover situations naturally. Additional [disaster recovery](https://fly.io/docs/litefs/backup/) options are available. * Sqlite3 databases are just files. Build a separate application to host - backups and have your application periodiacally POST copies there. + backups and have your application periodically POST copies there. * [Rsync](https://rsync.samba.org/) is a utility available with Linux distributions that can be used to efficiently copy changes between Machines. * Run multiple Machines per cell so that you get the full benefits of diff --git a/blueprints/going-to-production-with-healthcare-apps.html.md b/blueprints/going-to-production-with-healthcare-apps.html.md index b7ee2de288..83ce7acf44 100644 --- a/blueprints/going-to-production-with-healthcare-apps.html.md +++ b/blueprints/going-to-production-with-healthcare-apps.html.md @@ -13,7 +13,7 @@ redirect_from: /docs/blueprints/going-to-production-with-hipaa-apps Fly.io was built by security researchers from the ground up to be both productive and secure, making it a great home for HIPAA-compliant production healthcare applications for productive teams that ship often. -This guiide runs a developer or operations engineer through the process of evaluating Fly.io's security for HIPAA healthcare apps, launching a pilot application, signing a Business Associate Agreement (BAA), and deploying to production. +This guide runs a developer or operations engineer through the process of evaluating Fly.io's security for HIPAA healthcare apps, launching a pilot application, signing a Business Associate Agreement (BAA), and deploying to production. ## HIPAA and Fly.io Primer diff --git a/blueprints/shared-nothing.html.markerb b/blueprints/shared-nothing.html.markerb index e66f4c836b..d311968ef0 100644 --- a/blueprints/shared-nothing.html.markerb +++ b/blueprints/shared-nothing.html.markerb @@ -34,7 +34,7 @@ Over time, it grew out of my attic and onto VMs in the cloud. It supports more e If this approach isn’t the best one for your app, throw it out the window! I did. In my case, it made a lot of sense to put all the services into a single VM, and scale out by repeating that set into new VMs. This works great for me. Maybe it’s right for your app, too! Maybe not! Prepare to bathe in the gory details of my stateful, serverful, shared-nothing monolith. -## Shared-nothing architecures +## Shared-nothing architectures
A shared-nothing architecture is a distributed computing architecture in which each update request is satisfied by a single node (processor/memory/storage unit) in a computer cluster. diff --git a/blueprints/staging-prod-isolation.html.md b/blueprints/staging-prod-isolation.html.md index 8e40e08f25..d5a947ff84 100644 --- a/blueprints/staging-prod-isolation.html.md +++ b/blueprints/staging-prod-isolation.html.md @@ -33,7 +33,7 @@ It's best if you use one Fly.io account to manage all your organizations, so you ### Manage organizations in your dashboard -To create a new org from the [dashboard]((https://fly.io/dashboard/)), select **Create new organization** from the **Organization** dropdown. +To create a new org from the [dashboard](https://fly.io/dashboard/), select **Create new organization** from the **Organization** dropdown. To view or send invites to members, use the **Organization** dropdown to choose an org, then go to **Team**. diff --git a/js/prisma/postgres.html.md b/js/prisma/postgres.html.md index 8bf2c33d96..5dc1401f90 100644 --- a/js/prisma/postgres.html.md +++ b/js/prisma/postgres.html.md @@ -57,7 +57,7 @@ npx prisma migrate dev --name init Remove the `[processes]` and `[mounts]` sections from the `fly.toml` and add the `[deploy]` section you see above. -Download your existing SQLite database and use [pgloader](https://pgloader.readthedocs.io/en/latest/ref/sqlite.html) to covert it to postgres: +Download your existing SQLite database and use [pgloader](https://pgloader.readthedocs.io/en/latest/ref/sqlite.html) to convert it to postgres: ```bash fly sftp get /data/dev.db diff --git a/js/prisma/sqlite.html.md b/js/prisma/sqlite.html.md index f740ddf351..a24c9d312c 100644 --- a/js/prisma/sqlite.html.md +++ b/js/prisma/sqlite.html.md @@ -6,7 +6,7 @@ order: 1 --- Most Prisma demos use [SQLite](https://www.sqlite.org/index.html), as it will get you up and running fast. As an embedded database, it will run fast in production also, some -report anywhere from [10 to 600](https://www.youtube.com/watch?v=XcAYkriuQ1o) times faster that PostgreSQL. +report anywhere from [10 to 600](https://www.youtube.com/watch?v=XcAYkriuQ1o) times faster than PostgreSQL. Sqlite publishes a page of [appropriate uses of SQLite](https://www.sqlite.org/whentouse.html). There are few downsides to be aware of: diff --git a/js/shopify.html.markerb b/js/shopify.html.markerb index d17c1d12f9..605fe504a7 100644 --- a/js/shopify.html.markerb +++ b/js/shopify.html.markerb @@ -52,7 +52,7 @@ You can also [Scale Machine CPU and RAM](https://fly.io/docs/launch/scale-machin ## Database Shopify's template starts you off with SQLite using Prisma. Of particular note: - * By virtue of only running on a single Machine, SQLlite3 apps will experience brief unavailabilty during deploys. For a typical application without any new migrations, this will be on the order of a few hundred milliseconds. + * By virtue of only running on a single Machine, SQLlite3 apps will experience brief unavailability during deploys. For a typical application without any new migrations, this will be on the order of a few hundred milliseconds. * For PostgreSQL applications without any volumes, [rolling deploys](https://fly.io/docs/launch/deploy/#deployment-strategy) are the default, avoiding any downtime. Additional information is available on [deploying Prisma apps on Fly.io](../prisma/). diff --git a/litefs/faq.html.markerb b/litefs/faq.html.markerb index 4925e0ba9d..9d7a546f91 100644 --- a/litefs/faq.html.markerb +++ b/litefs/faq.html.markerb @@ -19,7 +19,7 @@ are close to users. This has a significant impact on reducing latency as application servers can process read requests from their local, on-disk database rather than communicating with a database server over the network. -It can also be used for replicating auxillery databases to a fleet of servers so +It can also be used for replicating auxiliary databases to a fleet of servers so that changes on the primary are immediately visible to replicas. These databases can include configuration information or they can include supplemental data like geospatial lookups. diff --git a/machines/api/volumes-resource.html.markerb b/machines/api/volumes-resource.html.markerb index 4560457578..71f0a6987e 100644 --- a/machines/api/volumes-resource.html.markerb +++ b/machines/api/volumes-resource.html.markerb @@ -322,7 +322,7 @@ Retrieve details about a specific volume by its ID within an app. ## Update a volume -Update paratemeters on the volume. +Update parameters on the volume.