diff --git a/pages/site/releases/2.16.md b/pages/site/releases/2.16.md
index 0c430be..72bc060 100644
--- a/pages/site/releases/2.16.md
+++ b/pages/site/releases/2.16.md
@@ -14,8 +14,6 @@
 
 ## Release Highlights
 
-* Support for git [protocol version 2](https://opensource.googleblog.com/2018/05/introducing-git-protocol-version-2.html).
-
 * GWT UI is deprecated, and PolyGerrit is now the default UI.
 
 * Experimental Dark Mode in PolyGerrit.
@@ -383,28 +381,6 @@
 It defaults to `false`, but one possible use case is to set the value to `true` for the `Code-Review` label in the `All-Projects` project.
 That value will then be inherited by all projects that do not override the `Code-Review` label settings.
 
-### Git protocol version 2 (experimental)
-
-Support for Git protocol version 2 is still experimental. Do not use it in
-production!
-
-Support for upload pack with git protocol version 2 can be enabled by
-setting `receive.enableProtocolV2` in `gerrit.config` and adding the
-configuration:
-
-```
-[protocol]
-  version = 2
-```
-
-either in the gerrit user's `~/.gitconfig` to enable for all repositories,
-or on a per repository basis in each repository's `config` file on the
-server.
-
-On the client side, the same `protocol.version` must be set either in
-the user's `~/.gitconfig` or in the repository's `.git/config` file.
-
-
 ## Dependency Updates
 
 * Update args4j to 2.33
@@ -517,6 +493,13 @@
 
 ### 2.16.2
 
+* [Change 208092](https://gerrit-review.googlesource.com/c/gerrit/+/208092):
+Disable support for Git protocol v2.
+
+  The JGit implementation of protocol V2 does not invoke the
+  advertiseRefsHook on fetch and ls-refs, which results in all
+  refs being sent, regardless of the configured ACLs.
+
 * [Issue 9024](https://bugs.chromium.org/p/gerrit/issues/detail?id=9024):
 Fix setting `PRIVATE` and `WIP` for updated changes in console report.
 
@@ -525,24 +508,23 @@
 
 * Fix case-insensitive searching of hashtags.
 
-* [Issue 9768](https://bugs.chromium.org/p/gerrit/issues/detail?id=9768):
-Explicitly set the number of shards and replicas for Elasticsearch, and
-allow them to be configured.
-
-  From Elasticsearch version 7 the default number of shards per node
-  will be changed from 5 to 1.
-
-  The number of shards and number of replicas are now explicitly set when
-  creating the index.
-
-  The new settings `elasticsearch.numberOfShards` and `elasticsearch.numberOfReplicas`
-  allow the values to be configured. The default values are 5 and 1,
-  respectively, which is the same as the default values used by Elasticsearch
-  prior to version 7.
-
 * [Issue 10106](https://bugs.chromium.org/p/gerrit/issues/detail?id=10106):
 Fix incorrect json in the example for the 'Set Access' REST endpoint.
 
+* [Issue 10112](https://bugs.chromium.org/p/gerrit/issues/detail?id=10112):
+Upgrade rules_closure to make Gerrit buildable with the latest Bazel version.
+
+* [Issue 9781](https://bugs.chromium.org/p/gerrit/issues/detail?id=9781):
+Fix full ACL evaluation for LDAP groups.
+
+  The LDAP groups have been historically filtered by relevance to
+  the Gerrit ACLs. However, that optimization has the side effect
+  of blocking users to access legitimate projects if they are
+  temporarily not cached in memory.
+  Allow to disable the LDAP filtering optimization for having always
+  a 100% consistent ACL evaluation, regardless of the project's cache
+  status.
+
 * Upgrade elasticsearch-rest-client to 6.5.3.
 
 * Discontinue support for Elasticsearch 2.4.
@@ -552,11 +534,6 @@
   Support for Elasticsearch 7 is added, and tested against the `alpha1`
   release.
 
-* [Issue 10112](https://bugs.chromium.org/p/gerrit/issues/detail?id=10112):
-Upgrade rules_closure to make Gerrit buildable with the latest Bazel version.
-
-* [Issue 9781](https://bugs.chromium.org/p/gerrit/issues/detail?id=9781):
-Allow to disable the groups relevance filtering for LDAP.
 
 * Add a new method on the account API to set the account name.