diff --git a/autodescription.php b/autodescription.php
index cca22c55..5d4bb6e9 100644
--- a/autodescription.php
+++ b/autodescription.php
@@ -3,7 +3,7 @@
  * Plugin Name: The SEO Framework
  * Plugin URI: https://theseoframework.com/
  * Description: An automated, advanced, accessible, unbranded and extremely fast SEO solution for your WordPress website.
- * Version: 5.1.1-beta-3
+ * Version: 5.1.1
  * Author: The SEO Framework Team
  * Author URI: https://theseoframework.com/
  * License: GPLv3
diff --git a/readme.txt b/readme.txt
index c8129e20..5e8da9a3 100644
--- a/readme.txt
+++ b/readme.txt
@@ -5,7 +5,7 @@ Tags: seo, xml sitemap, google search, open graph, structured data
 Requires at least: 6.0
 Tested up to: 6.7
 Requires PHP: 7.4.0
-Stable tag: 5.1.0
+Stable tag: 5.1.1
 License: GPLv3
 License URI: http://www.gnu.org/licenses/gpl-3.0.html
 
@@ -245,25 +245,7 @@ You can also output these breadcrumbs visually in your theme by [using a shortco
 
 ### 5.1.1
 
-This tiny update [fixes issues](https://theseoframework.com/?p=4348) our community found after the release of TSF v5.1.
-
-**For everyone:**
-
-* **Fixed:** Resolved a fatal error that occurred when saving a user profile.
-* **Fixed:** Resolved an issue where the user meta sanitizer didn't invoke. Now, Facebook and X (formerly Twitter) handles will be sanitized properly again. This issue was introduced in TSF v5.0.
-	* This means that the Facebook page and X handle will now be correctly converted again to what Facebook and X expect. If you mimicked the placeholder, then the input was already correct.
-	* Only users who can edit posts can have these handles. You'll need to re-save these profiles to apply the sanitization.
-	* We considered sanitizing when outputting the handles, instead of when storing them, but the sanitization process is resource intensive. Moreover, we have not determined the efficacy of these social profile handles; we only added them because the social networks want them. They don't appear to even use them. So, the extra processing would be futile.
-	* We always escape all data on output. This was not a security issue.
-* **Fixed:** Resolved an issue where the Canonical URL Notation Tracker didn't consider categories on new posts.
-	* In turn, TSF makes an extra AJAX call when you add a new post, for TSF relies on the primary term to select the right category, which is currently only calculable in the editor for new posts. We'll look at improving this in the future.
-
-**For developers:**
-
-* **Changed** PHP method `The_SEO_Framework\Data\User::get_userdata()` (`tsf()->data()->user()->get_userdata()`):
-	1. The second parameter is now nullable and `null` by default.
-	1. Can now return the `WP_User` object as well when the second parameter is `null`.
-* **Changed:** JS object `tsfPost.l10n` now has property `supportedTaxonomies`, which is an array of supported taxonomies.
+This tiny update [resolves issues](https://theseoframework.com/?p=4348) our community found with the release of TSF v5.1.
 
 ### 5.1.0 - Profound