Update readme. (ampproject#343)

Fix formatting error, and change future tense to present.

README.md

@@ -1,14 +1,14 @@
 # AMP Packager
 
-AMP Packager is a tool to [improve AMP        
-URLs](https://blog.amp.dev/2018/11/13/developer-preview-of-better-amp-urls-in-google-search/) by [serving AMP using Signed Exchanges](https://amp.dev/documentation/guides-and-tutorials/optimize-and-measure/signed-exchange/). By running it
-in a proper configuration, web publishers may (eventually) have origin URLs
+AMP Packager is a tool to [improve AMP URLs](https://blog.amp.dev/2018/11/13/developer-preview-of-better-amp-urls-in-google-search/)
+by [serving AMP using Signed Exchanges](https://amp.dev/documentation/guides-and-tutorials/optimize-and-measure/signed-exchange/).
+By running it in a proper configuration, web publishers enable origin URLs to
 appear in AMP search results.
 
 The AMP Packager works by creating [Signed HTTP
 Exchanges (SXGs)](https://wicg.github.io/webpackage/draft-yasskin-httpbis-origin-signed-exchanges-impl.html)
 containing AMP documents, signed with a certificate associated with the origin,
-with a maximum lifetime of 7 days. In the future, the [Google AMP
+with a maximum lifetime of 7 days. The [Google AMP
 Cache](https://amp.dev/documentation/guides-and-tutorials/learn/amp-caches-and-cors/how_amp_pages_are_cached/) will fetch,
 cache, and serve them, similar to what it does for normal AMP HTML documents.
 When a user loads such an SXG, Chrome validates the signature and then displays