Fix inconsistent indentation in 2.14 release notes
Change-Id: Ifc64b653307af14a47eec5a41d4f30b13e1688bb
diff --git a/releases/2.14.md b/releases/2.14.md
index fea4f06..9a263e3 100644
--- a/releases/2.14.md
+++ b/releases/2.14.md
@@ -203,18 +203,18 @@
Prevent `ref-update` hook from being invoked on every commit when pushing
multiple commits.
- Instead of being invoked on every commit received, the `ref-update` hook
- is now invoked before the ref update operation is finalized. Note that
- the hook is no longer invoked on commits pushed for review or on changes
- that are merged. It is invoked for creation/deletion of refs, and for
- ref updates caused by direct pushes (i.e. bypassing review).
+ Instead of being invoked on every commit received, the `ref-update` hook
+ is now invoked before the ref update operation is finalized. Note that
+ the hook is no longer invoked on commits pushed for review or on changes
+ that are merged. It is invoked for creation/deletion of refs, and for
+ ref updates caused by direct pushes (i.e. bypassing review).
- The previous behavior of the `ref-update` hook is moved into a new hook
- named `commit-received`. A new parameter `--cmdref` is added, and the
- special handling of `refs/for` and `refs/changes` is removed.
+ The previous behavior of the `ref-update` hook is moved into a new hook
+ named `commit-received`. A new parameter `--cmdref` is added, and the
+ special handling of `refs/for` and `refs/changes` is removed.
- Sites using the `ref-update` hook should rename the hook file to
- `commit-received`.
+ Sites using the `ref-update` hook should rename the hook file to
+ `commit-received`.
## Dependency Updates
@@ -335,12 +335,12 @@
* [Issue 6176](https://bugs.chromium.org/p/gerrit/issues/detail?id=6176):
Fix internal server error when old patch set is not found.
-* Always use SSL implicitly for POP3 and IMAP.
+* Always use SSL implicitly for POP3 and IMAP.
- If `receiveemail.encryption` is set to TLS/SSL, we always want to use the
- implicit mode to execute the TLS/SSL command right after establishing
- the conection with the mail server. Strict mail servers like Gmail would
- close the connection prematurely otherwise.
+ If `receiveemail.encryption` is set to TLS/SSL, we always want to use the
+ implicit mode to execute the TLS/SSL command right after establishing
+ the conection with the mail server. Strict mail servers like Gmail would
+ close the connection prematurely otherwise.
* Allow plugins to non-transitively depend on prolog rules.
