diff --git a/_config.yml b/_config.yml
index 105fe7f5ed2..602bdb5d3ee 100644
--- a/_config.yml
+++ b/_config.yml
@@ -111,7 +111,7 @@ social:
 current_major_version: 2024
 current_minor_version: 1
 current_patch_version: 0
-date_released: 2023-01-03
+date_released: 2024-01-03
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.
diff --git a/source/_posts/2024-01-03-release-20241.markdown b/source/_posts/2024-01-03-release-20241.markdown
index caee8b895d4..d3d96c9146b 100644
--- a/source/_posts/2024-01-03-release-20241.markdown
+++ b/source/_posts/2024-01-03-release-20241.markdown
@@ -142,8 +142,7 @@ service calls.
 If you have been using Home Assistant for a while, you are probably familiar
 with the “service call”-an action that you can add to your automation. But,
 honestly, what is a “service call”? It is a bit of a technical term that is
-especially confusing for newer users. But honestly, you just want to turn on
-a light, right?
+especially confusing for newer users. You just want to turn on a light, right?
 
 This release unifies those “service calls” with all other actions, meaning
 there is no “service call” anymore; that layer has been refactored from the UI.
@@ -540,7 +539,7 @@ If you want to go back to the light domain, use the
 [switch_as_x "Show as" option](/integrations/switch_as_x/#change-device-type-of-a-switch-from-the-existing-entity)
 on the new `Infrared lights in night mode` switch entity and select light.
 
-([@starkillerOG] - [#104713]) ([documentation](/integrations/reolink))
+([@starkillerOG] - [#105916]) ([documentation](/integrations/reolink))
 
 [@starkillerOG]: https://github.com/starkillerOG
 [#105916]: https://github.com/home-assistant/core/pull/105916
diff --git a/source/images/blog/2024-01/social.png b/source/images/blog/2024-01/social.png
index ea06706893c..bac68c31a55 100644
Binary files a/source/images/blog/2024-01/social.png and b/source/images/blog/2024-01/social.png differ