From 7a767f721960d92366a512f4f096a055fa4d2e9e Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Fri, 27 Apr 2018 05:57:46 -0400 Subject: [PATCH] typos --- TROUBLESHOOTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/TROUBLESHOOTING.md b/TROUBLESHOOTING.md index 532aff6838ce..15ed7e5deb50 100644 --- a/TROUBLESHOOTING.md +++ b/TROUBLESHOOTING.md @@ -52,7 +52,7 @@ There may be multiple sources for classpath conflicts: For example, if you have a direct or a transitive dependency on Guava version 10.0, and also `google-cloud-java` uses Guava version 20.0, then `google-cloud-java` could be using Guava methods that don't exist in Guava 10.0, and could cause `NoSuchMethodError`. -Similarily, if your classpath has an older version of `protobuf-java`, but `google-cloud-java` requires newer version, then you may see `NoClassDefFoundError` that fails to initialize `google-cloud-java` classes, e.g.: +Similarily, if your classpath has an older version of `protobuf-java`, but `google-cloud-java` requires a newer version, then you may see `NoClassDefFoundError` that fails to initialize `google-cloud-java` classes, e.g.: ``` java.lang.NoClassDefFoundError: Could not initialize class com.google.pubsub.v1.PubsubMessage$AttributesDefaultEntryHolder @@ -72,7 +72,7 @@ If you experience the error only during runtime, then it means that your runtime ### Detecting the conflict early during build -To detect dependnecy version conflicts early, use the [Enforcer Plugin](https://maven.apache.org/enforcer/maven-enforcer-plugin/index.html) in your Maven configuration to enforce dependency convergence: +To detect dependency version conflicts early, use the [Enforcer Plugin](https://maven.apache.org/enforcer/maven-enforcer-plugin/index.html) in your Maven configuration to enforce dependency convergence: ```