From 71524aba8cd7bee794ac0f7567544c1b177cdec3 Mon Sep 17 00:00:00 2001
From: "Matthias J. Sax" <matthias@confluent.io>
Date: Mon, 16 Jul 2018 14:19:24 -0700
Subject: [PATCH] MINOR: improve versions

---
 10/upgrade.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/10/upgrade.html b/10/upgrade.html
index 2d53cd563a5..639ccc86bfd 100644
--- a/10/upgrade.html
+++ b/10/upgrade.html
@@ -131,8 +131,8 @@ <h5><a id="upgrade_100_new_protocols" href="#upgrade_100_new_protocols">New Prot
 
 <h5><a id="upgrade_100_streams_from_0110" href="#upgrade_100_streams_from_0110">Upgrading a 0.11.0 Kafka Streams Application</a></h5>
 <ul>
-    <li> Upgrading your Streams application from 0.11.0 to 1.0.0 does not require a broker upgrade.
-         A Kafka Streams 1.0.0 application can connect to 0.11.0, 0.10.2 and 0.10.1 brokers (it is not possible to connect to 0.10.0 brokers though).
+    <li> Upgrading your Streams application from 0.11.0 to 1.0 does not require a broker upgrade.
+         A Kafka Streams 1.0 application can connect to 0.11.0, 0.10.2 and 0.10.1 brokers (it is not possible to connect to 0.10.0 brokers though).
          However, Kafka Streams 1.0 requires 0.10 message format or newer and does not work with older message formats. </li>
     <li> If you are monitoring on streams metrics, you will need make some changes to the metrics names in your reporting and monitoring code, because the metrics sensor hierarchy was changed. </li>
     <li> There are a few public APIs including <code>ProcessorContext#schedule()</code>, <code>Processor#punctuate()</code> and <code>KStreamBuilder</code>, <code>TopologyBuilder</code> are being deprecated by new APIs.