Replaced 'git' with 'Git' in the prose

docs/configuration/builders.md

@@ -60,7 +60,7 @@ The image is only used for registry cache and is not compatible with the Docker
 
 ## [Build context](#build-context)
 
-If this is not set, then a local git clone of the repo is used. This ensures a clean build with no uncommitted changes.
+If this is not set, then a local Git clone of the repo is used. This ensures a clean build with no uncommitted changes.
 
 To use the local checkout instead, you can set the context to `.`, or a path to another directory.
 

docs/installation/index.md

@@ -65,7 +65,7 @@ This will:
 5. Push the image to the registry.
 6. Pull the image from the registry onto the servers.
 7. Ensure kamal-proxy is running and accepting traffic on ports 80 and 443.
-8. Start a new container with the version of the app that matches the current git version hash.
+8. Start a new container with the version of the app that matches the current Git version hash.
 9. Tell kamal-proxy to route traffic to the new container once it is responding with `200 OK` to `GET /up`.
 10. Stop the old container running the previous version of the app.
 11. Prune unused images and stopped containers to ensure servers don't fill up.

v1/docs/commands/build.md

@@ -6,7 +6,7 @@ title: Build
 
 Build your app images and push them to your servers. These commands are called indirectly by `kamal deploy` and `kamal redeploy`.
 
-By default, Kamal will only build files you have committed to your git repository. However, you can configure Kamal to use the current context (instead of a git archive of HEAD) by setting the [build context](https://kamal-deploy.org/docs/configuration/builders/#build-context).
+By default, Kamal will only build files you have committed to your Git repository. However, you can configure Kamal to use the current context (instead of a Git archive of HEAD) by setting the [build context](https://kamal-deploy.org/docs/configuration/builders/#build-context).
 
 ```bash
 $ kamal build

v1/docs/commands/envify.md

@@ -23,7 +23,7 @@ MYSQL_ROOT_PASSWORD=<%= `op read "op://Vault/My App/MYSQL_ROOT_PASSWORD" -n --se
 <% else raise ArgumentError, "Session token missing" end %>
 ```
 
-This template can safely be checked into git. Then everyone deploying the app can run `kamal envify` when they setup the app for the first time or passwords change to get the correct `.env` file.
+This template can safely be checked into Git. Then everyone deploying the app can run `kamal envify` when they setup the app for the first time or passwords change to get the correct `.env` file.
 
 If you need separate env variables for different destinations, you can set them with `.env.destination.erb` for the template, which will generate `.env.staging` when run with `kamal envify -d staging`.
 

v1/docs/configuration/builders.md

@@ -62,7 +62,7 @@ The type must be either 'gha' or 'registry'. The image is only used for registry
 
 ## [Build context](#build-context)
 
-If this is not set, then a local git clone of the repo is used. This ensures a clean build with no uncommitted changes.
+If this is not set, then a local Git clone of the repo is used. This ensures a clean build with no uncommitted changes.
 
 To use the local checkout instead you can set the context to `.`, or a path to another directory:
 

v1/docs/installation/index.md

@@ -60,7 +60,7 @@ This will:
 7. Push the ENV variables from .env onto the servers.
 8. Ensure Traefik is running and accepting traffic on port 80.
 9. Ensure your app responds with `200 OK` to `GET /up` (you must have curl installed inside your app image!).
-10. Start a new container with the version of the app that matches the current git version hash.
+10. Start a new container with the version of the app that matches the current Git version hash.
 11. Stop the old container running the previous version of the app.
 12. Prune unused images and stopped containers to ensure servers don't fill up.