diff --git a/_kbarticles/2024-12-09-apt-buildpack-cache-issue.md b/_kbarticles/2024-12-09-apt-buildpack-cache-issue.md
index 458ce5a8e..f852abe84 100644
--- a/_kbarticles/2024-12-09-apt-buildpack-cache-issue.md
+++ b/_kbarticles/2024-12-09-apt-buildpack-cache-issue.md
@@ -13,7 +13,7 @@ Different buildpacks use this cache for different things. [System buildpacks]({%
 
 ### Potential cache issue with apt-buildpack 
 
-The potential issue involves the `/` directory disk allocation. The apt buildpack uses `/tmp` like other buildpacks. The `/` directory is allocated approximately 9% of the disk allocation. For most buildpacks, this is sufficient as all the possible packages that they could be installing is known with the only variable being the application code. The apt buildpack however, can install a vast number of large packages, suchas  the AWS CLI. Depending on how many packages are installed and their individual size, the allotted 9% of disk space may not be sufficient.
+The potential issue with the `apt-buildpack` cache involves the `/` directory disk allocation. The `apt-buildpack` uses `/tmp` for its cache like other buildpacks. In all buildpacks, the `/` directory is allocated approximately 9% of the disk allocation, meaning that the size of the `/tmp` subdirectory cannot exceed that disk allocation. For most buildpacks, this disk allocation is sufficient as all the possible packages that they could be installing is known with the only variable being the application code. However, the `apt-buildpack` can install an unknown number of packages of variable size, such as the AWS CLI. Depending on how many packages are installed and their individual size, the allotted 9% of disk space may not be sufficient, causing application staging to fail.
 
 ### How to address the issue