From c09d4b01980c14ebf29e8e391b6020c22eae479f Mon Sep 17 00:00:00 2001
From: Jason Zou <43589197+zoujas@users.noreply.github.com>
Date: Thu, 4 Jan 2024 20:28:05 -0500
Subject: [PATCH] Update load-test-with-java.md

---
 en/load/load-test-with-java.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/en/load/load-test-with-java.md b/en/load/load-test-with-java.md
index 6563f7a..117159d 100644
--- a/en/load/load-test-with-java.md
+++ b/en/load/load-test-with-java.md
@@ -11,7 +11,7 @@ Our browserup/standard image ships with Java pre-installed.
 
 If you have a code library that makes HTTP/Websocket requests, you can call
 your library directly to make requests on your behalf. For example, if you
-have an internal client library for a REST api, you can use your own library to
+have an internal client library for a REST API, you can use your own library to
 generate load with <span style="font-weight: bold; color: #de792b;">Browser</span><span style="font-weight: bold; color: #6e6e6e;">Up</span> while capturing your traffic.
 
 The key advantages to doing this with <span style="font-weight: bold; color: #de792b;">Browser</span><span style="font-weight: bold; color: #6e6e6e;">Up</span> are:
@@ -22,7 +22,7 @@ The key advantages to doing this with <span style="font-weight: bold; color: #de
 
 There are two approaches to creating this type of test:
 
-* Use our standard image with a FAT Jar. A Fat JAR is compiled with all
+* Use our standard image with a FAT Jar. A FAT JAR is compiled with all
 dependencies built into the Jar. For this approach, your app will be run with our
 built-in Java (OpenJDK 17)
 
@@ -52,7 +52,5 @@ you won't necessarily need to create a FAT jar (although that's fine as well).
 At present, the base for the custom image must be our browserup/custom-base image, which is built on Debian Bookworm Slim.
 
 So simply start your Dockerfile with:
-browserup/custom-base
-
-Then install your dependencies as needed.
+browserup/custom-base, then install your dependencies as needed.