Fixed a structural bug on the release note.

Minor corrections with spelling and grammar.

Author: RayOffiah

modules/release-notes/partials/docs-server-7.6.4-release-note.adoc

@@ -25,7 +25,7 @@ This release contains the following fixes:
 | Issue resolved.
 
 | https://jira.issues.couchbase.com/browse/MB-62413[MB-62413]
-| When a username is extracted from a client certificate, the candidate username is checked for its existance in couchbase-server. If such user doesn't exist, algorithm now doesn't stop, but tries to extract another candidate username.
+| When a username is extracted from a client certificate, the candidate username is checked for its existence in couchbase-server. If such a user doesn't exist, the algorithm now doesn't stop but tries to extract another candidate username.
 |Issue resolved.
 
 | https://jira.issues.couchbase.com/browse/MB-63981[MB-63871]
@@ -101,7 +101,7 @@ a| In previous versions of Couchbase Server, a clear delimiter between a numeric
 
    * Prevent stream completion.
 
-   * Block access to the system:vitals keyspace or vitals end-point.
+   * Block access to the system:vitals keyspace or `vitals` end-point.
 
    * Require a full Query process restart on affected nodes as the only previous workaround.
 
@@ -165,17 +165,21 @@ The issue occurred only with partitioned indexes with file-based rebalances enab
 |Issue | Description | Resolution
 
 | https://jira.issues.couchbase.com/browse/MB-62427[MB-62427]
-| In index definitions from version 6.x, the `segmentVersion` parameter is absent, with it previously defaulting to v11. With 7.6 we’ve updated the default to v16. So when the `segmentVersion` is absent, the v16 code will be going into effect.
+a| In index definitions from version 6.x, the `segmentVersion` parameter is absent, with it previously defaulting to v11.
+With 7.6 we’ve updated the default to v16.
+So when the `segmentVersion` is absent, the v16 code will be going into effect.
 
-An issue in the v16 code while interpreting data with no vector fields caused an alignment panic. This panic is fixed with 7.6.4 allowing 6.x index definitions to work ok in 7.6.4.
+An issue in the v16 code while interpreting data with no vector fields caused an alignment panic.
+This panic is fixed with 7.6.4, allowing 6.x index definitions to work ok in 7.6.4.
 
-   * This problem occurs only for index definitions that survive an upgrade from 6.x to 7.x and then 7.6.x without being “re-built” meaning they’d still be using the v11 file format.
+* This problem occurs only for index definitions that survive an upgrade from 6.x to 7.x and then 7.6.x without being “re-built” meaning they’d still be using the v11 file format.
 
-   * Indexes that were introduced in server version 7.x and later or re-built after the cluster was fully upgraded to 7.x (which will have a segmentVersion:15 setting within their index definition) will not encounter this issue, because they invoke the v15 code.
+* Indexes that were introduced in server version 7.x and later or re-built after the cluster was fully upgraded to 7.x, (which will have a segmentVersion:15 setting within their index definition) will not encounter this issue, because they invoke the v15 code.
 
-| In summary, version 7.6.4 now supports upgrades of 6.x index definitions. However, Couchbase recommends upgrading indexes to 15+ segment version format for improvements in indexing footprint and performance.
-
-| Issue resolved.
+| In summary, version 7.6.4 now supports upgrades of 6.x index definitions. 
+However,
+Couchbase recommends upgrading indexes to 15+ segment version format for improvements in indexing footprint and performance. +
+Issue resolved.
 
 |===