diff --git a/.github/workflows/performance-test.yml b/.github/workflows/performance-test.yml
index ad3b843dd12..1ec537a0b4f 100644
--- a/.github/workflows/performance-test.yml
+++ b/.github/workflows/performance-test.yml
@@ -88,7 +88,7 @@ jobs:
       - name: Build graph
         if: matrix.profile == 'core' || github.ref == 'refs/heads/dev-2.x'
         run: |
-          cp application/target/otp-*-SNAPSHOT-shaded.jar otp.jar
+          cp shaded-jar/target/otp-*-SNAPSHOT-shaded.jar otp.jar
           java -Xmx32G -jar otp.jar --build --save test/performance/${{ matrix.location }}/
 
       - name: Run speed test
diff --git a/README.md b/README.md
index 41d889cf15b..ec66e694e8c 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,7 @@ We run a speed test (included in the code) to measure the performance for every
 The main Java server code is in `application/src/main/`. OTP also includes a Javascript client based on the
 MapLibre mapping library in `client/src/`. This client is now used for testing, with most major
 deployments building custom clients from reusable components. The Maven build produces a unified ("shaded")
-JAR file at `application/target/otp-VERSION.jar` containing all necessary code and dependencies to run OpenTripPlanner.
+JAR file at `shaded-jar/target/otp-VERSION.jar` containing all necessary code and dependencies to run OpenTripPlanner.
 
 Additional information and instructions are available in
 the [main documentation](http://docs.opentripplanner.org/en/dev-2.x/), including a
diff --git a/doc/user/Getting-OTP.md b/doc/user/Getting-OTP.md
index 92f1e7298fc..ea0bac0df90 100644
--- a/doc/user/Getting-OTP.md
+++ b/doc/user/Getting-OTP.md
@@ -65,7 +65,7 @@ OTP. If all goes well you should see a success message like the following:
 ```
 
 This build process should produce a JAR file called `otp-x.y.z-shaded.jar` in the
-`application/target/` directory which contains all the compiled OTP classes and their dependencies
+`shaded-jar/target/` directory which contains all the compiled OTP classes and their dependencies
 (the external libraries they use). The shell script called 'otp' in the root of the cloned repository
 will start the main class of that JAR file under a Java virtual machine, so after the Maven build
 completes you should be able to run `./otp --help` and see an OTP help message including command line