From f9dd0f45ab030b71956cf6c17e0087b76f642a40 Mon Sep 17 00:00:00 2001 From: David Whittam <84255659+OneAutumnMango@users.noreply.github.com> Date: Wed, 7 Feb 2024 19:55:15 +0000 Subject: [PATCH] Minor spelling fix in auto-curseforge.md (#2642) --- docs/types-and-platforms/mod-platforms/auto-curseforge.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/types-and-platforms/mod-platforms/auto-curseforge.md b/docs/types-and-platforms/mod-platforms/auto-curseforge.md index 1c25de4f..70f60d54 100644 --- a/docs/types-and-platforms/mod-platforms/auto-curseforge.md +++ b/docs/types-and-platforms/mod-platforms/auto-curseforge.md @@ -97,7 +97,7 @@ For mod, modpacks, and world files that are not allowed for automated download, 1. Create a directory next to the `docker-compose.yml` file. The name doesn't matter, but "downloads" is the common convention 2. From the "Mods Need Download" output, visit the download page of each, click on the file download and save that file into the directory created in the previous step 3. Add a host directory mount to the volumes section where the container path **must be** `/downloads`. The snippet below shows how that will look - 4. Re-run `docker composwe up -d` to apply the changes + 4. Re-run `docker compose up -d` to apply the changes ```yaml volumes: @@ -106,7 +106,7 @@ For mod, modpacks, and world files that are not allowed for automated download, ## Unpublished Modpacks -If you wish to use a unpublished modpack zip, set the container path to the file in `CF_MODPACK_ZIP`. Similarly, the container path to a modpack manifest JSON can be passed to `CF_MODPACK_MANIFEST`. In either case, **the modpack slug or page URL must still be provided**. +If you wish to use an unpublished modpack zip, set the container path to the file in `CF_MODPACK_ZIP`. Similarly, the container path to a modpack manifest JSON can be passed to `CF_MODPACK_MANIFEST`. In either case, **the modpack slug or page URL must still be provided**. !!! example