From fcf6391786f10dd0e463c98e867e9c92f17d88d7 Mon Sep 17 00:00:00 2001 From: PlanetScale Actions Bot Date: Sat, 4 Nov 2023 13:35:17 +0000 Subject: [PATCH] docs: upstream https://github.com/planetscale/www/commit/8971b9b5f8972b046868e55b1320119b3aaf4712 --- docs/tutorials/connect-go-gorm-app.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials/connect-go-gorm-app.md b/docs/tutorials/connect-go-gorm-app.md index 28c982b2..3e74eb32 100644 --- a/docs/tutorials/connect-go-gorm-app.md +++ b/docs/tutorials/connect-go-gorm-app.md @@ -230,7 +230,7 @@ You can now refresh the [Go products page](http://localhost:8080/products) to se ## What's next? -Once you're done with initial development, you can enable [safe migrations](/docs/concepts/safe-migrations) on your `main` production branch to protect it against direct schema changes and enable zero-downtime schema migraions. +Once you're done with initial development, you can enable [safe migrations](/docs/concepts/safe-migrations) on your `main` production branch to protect it against direct schema changes and enable zero-downtime schema migrations. When you're reading to make more schema changes, you'll [create a new branch](/docs/concepts/branching) off of your production branch. Branching your database creates an isolated copy of your production schema so that you can easily test schema changes in development. Once you're happy with the changes, you'll open a [deploy request](/docs/concepts/deploy-requests). This will generate a diff showing the changes that will be deployed, making it easy for your team to review.