chore(docs): Fix typos and add a note about DATABASE_USE_IPV6 to the …

…release notes (#1264)

docs/reference/release_notes.md

@@ -20,11 +20,11 @@ To see the complete change log for each new release, see the [Releases page](htt
 - [@electric-sql/prisma-generator](https://github.com/electric-sql/electric/blob/main/generator/CHANGELOG.md)
 
 
-## 2024-05-02 - v0.11
+## 2024-05-14 - v0.11
 
 [Announcement post](/blog/2024/05/14/electricsql-postgres-client-support).
 
-This release introduces a new database driver for PGLite, enabling client applications to use a local Postgres database. It also the first release to maintain replication stream continuity in the face of the sync service's restarts.
+This release introduces a new database driver for PGLite, enabling client applications to use a local Postgres database. It is also the first release to maintain replication stream continuity in the face of the sync service's restarts.
 
 #### Updated components
 
@@ -38,7 +38,9 @@ Component | Version
 
 **Sync service**
 
-- Electric no longer tries decode the JWT signing key by default. A new configuration option `AUTH_JWT_KEY_IS_BASE64_ENCODED` has been added to let the developer choose whether Electric should use the configured signing key as is or base64-decode it first.
+- Electric no longer tries to decode the JWT signing key by default. A new configuration option `AUTH_JWT_KEY_IS_BASE64_ENCODED` has been added to let the developer choose whether Electric should use the configured signing key as is or base64-decode it first.
+
+- The default value for `DATABASE_USE_IPV6` is now `false`. Using IPv6 by default turned out to cause problems that could have been avoided by sticking to IPv4. ISPs, Docker, hosting platforms do not all have seamless IPv6 support just yet.
 
 ## 2024-04-10 - v0.10