From d73de5dcad285be0c089fdaa87127c8769f021df Mon Sep 17 00:00:00 2001 From: Said Tahsin Dane Date: Tue, 4 Jun 2019 07:03:17 +0200 Subject: [PATCH] Update UPGRADING_TO_OKHTTP_4.md --- UPGRADING_TO_OKHTTP_4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UPGRADING_TO_OKHTTP_4.md b/UPGRADING_TO_OKHTTP_4.md index 9457a5708..c0b759aa8 100644 --- a/UPGRADING_TO_OKHTTP_4.md +++ b/UPGRADING_TO_OKHTTP_4.md @@ -11,7 +11,7 @@ keeping the package name the same: `okhttp3`! There are three kinds of compatibility we're tracking: * **Binary compatibility** is the ability to compile a program against OkHttp 3.x, and then to run - it against OkHttp 4.x. We're using use the excellent [japicmp][japicmp] library via its + it against OkHttp 4.x. We're using the excellent [japicmp][japicmp] library via its [Gradle plugin][japicmp_gradle] to enforce binary compatibility. * **Java source compatibility** is the ability to upgrade Java uses of OkHttp 3.x to 4.x without