diff --git a/docs/best-practices/java-coding-guidelines/readme.md b/docs/best-practices/java-coding-guidelines/readme.md
index 7a0e07c34..656b04a8d 100644
--- a/docs/best-practices/java-coding-guidelines/readme.md
+++ b/docs/best-practices/java-coding-guidelines/readme.md
@@ -1760,7 +1760,7 @@ public FooResource(String name) {
 }
 ```
 
-Acyclic dependency graphs are hard to understand, hard to setup for tests and mocks, and introduce subtle code ordering
+Circular dependency graphs are hard to understand, hard to setup for tests and mocks, and introduce subtle code ordering
 constraints. For example, switching the order of the constructor statements introduces a bug where the resource name is
 always "FooResource on port 0" since `Server#port` hasn't been initialized when the resource calls `Server#port()`: