diff --git a/releases/2.14.md b/releases/2.14.md
index 75209a3..a90eedf 100644
--- a/releases/2.14.md
+++ b/releases/2.14.md
@@ -29,7 +29,7 @@
 * New [Polymer](https://www.polymer-project.org/) based user interface
 * Support for elliptic curve/ed25519 SSH keys
 * Secondary index for groups
-* Experimental support for Elasticsearch as secondary index
+* Experimental support for Elasticsearch as secondary index **from [2.14.8](#2.14.8)**
 
 ## Important Notes
 
@@ -343,6 +343,12 @@
 
 ### 2.14.8 *(in development)* {#2.14.8}
 
+* Elasticsearch is now available for early adopters as a secondary index.
+
+  * The implementation is limited to version 2.4.x of Elasticsearch.
+
+  * See the list of [fixed issues](#elasticsearch) below for more details.
+
 * Expose plugin guice injectors in plugin test classes that derived from
 `LightweightPluginDaemonTest` base class.
 
@@ -373,6 +379,26 @@
 * [Issue 8731](https://bugs.chromium.org/p/gerrit/issues/detail?id=8731):
 Improve the wording in the revert notification email template.
 
+* [Issue 8589](https://bugs.chromium.org/p/gerrit/issues/detail?id=8589):
+Remove approval requirement search from basic search documentation.
+
+  Using approval requirements in basic search, for example `Code-Review=2`
+  without the explicit `label:` predicate can never work as expected because
+  the query is also considered as a comment search, which matches on all
+  changes that have received a vote on that label, regardless of the label
+  score.
+
+  The section about approval requirements is removed from the basic search
+  documentation to avoid confusion. It is also now recommended to use explicit
+  query predicates when predictable results are desired.
+
+* [Issue 8597](https://bugs.chromium.org/p/gerrit/issues/detail?id=8597):
+Clarify the behavior of `ownerin:` and `reviwerin:` queries.
+
+  When the ownerin: or reviewerin: predicate is used in a query without any
+  additional explicit index predicate, it will default to only include changes
+  in status 'OPEN'.
+
 * Fix internal server error when using the `query:` search with a non-existing
 named query.
 
@@ -390,7 +416,7 @@
   maximum period of time for the daemon to preserve incoming connections,
   before starting the graceful shutdown process.
 
-* Elasticsearch fixes
+* Elasticsearch {#elasticsearch}
 
   * [Issue 8523](https://bugs.chromium.org/p/gerrit/issues/detail?id=8523):
   Fix configuration of elasticsearch during site initialization.