diff --git a/Gemfile b/Gemfile
index 6ae166847d3..9da1b1dbb2b 100644
--- a/Gemfile
+++ b/Gemfile
@@ -11,7 +11,7 @@ group :development do
   # > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
   gem 'sassc', '2.1.0'
   gem 'sass-embedded', '1.83.4'
-  gem 'rubocop', '1.70.0'
+  gem 'rubocop', '1.71.0'
   gem 'ruby-lsp', '0.23.6'
   gem 'rackup', '2.2.1'
 end
diff --git a/Gemfile.lock b/Gemfile.lock
index 00aecb10401..738e2f639f5 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -114,7 +114,7 @@ GEM
     regexp_parser (2.10.0)
     rexml (3.4.0)
     rouge (4.5.1)
-    rubocop (1.70.0)
+    rubocop (1.71.0)
       json (~> 2.3)
       language_server-protocol (>= 3.17.0)
       parallel (~> 1.10)
@@ -151,7 +151,7 @@ GEM
       rack-protection (= 4.1.1)
       rack-session (>= 2.0.0, < 3)
       tilt (~> 2.0)
-    sorbet-runtime (0.5.11766)
+    sorbet-runtime (0.5.11778)
     stringex (2.8.6)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)
@@ -177,7 +177,7 @@ DEPENDENCIES
   nokogiri (= 1.18.2)
   rackup (= 2.2.1)
   rake (= 13.2.1)
-  rubocop (= 1.70.0)
+  rubocop (= 1.71.0)
   ruby-lsp (= 0.23.6)
   sass-embedded (= 1.83.4)
   sass-globbing (= 1.1.5)
diff --git a/source/_integrations/acaia.markdown b/source/_integrations/acaia.markdown
index 1ea74fc2461..7a5506d6e64 100644
--- a/source/_integrations/acaia.markdown
+++ b/source/_integrations/acaia.markdown
@@ -34,19 +34,19 @@ Device:
   description: "The Bluetooth device that is your scale."
 {% endconfiguration_basic %}
 
-# Available platforms & entities
+## Available platforms & entities
 
-## Binary sensors
+### Binary sensors
 
 - **Timer running**: Whether the timer is currently running on the scale
 
-## Buttons
+### Buttons
 
 - **Tare**: Tares the scale.
 - **Reset timer**: Resets the timer. If the timer is running, it will continue to run.
 - **Start/stop timer**: Starts or stops the timer, depending on whether the timer is currently running. Does not reset, but continue the timer.
 
-## Sensors
+### Sensors
 
 - **Battery**: Current battery level of the scale.
 - **Volume flow rate**: Calculates the current flow rate (in mL/s) while brewing.
diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown
index 43938fcad71..02dbd94583f 100644
--- a/source/_integrations/nest.markdown
+++ b/source/_integrations/nest.markdown
@@ -625,3 +625,9 @@ logger:
 ```
 
 - *Not receiving camera motion and person events*: assuming the integration is correctly configured (for example, the oauth and SDM API are set up correctly, you can see camera streams, and permissions are correctly set in [Partner Connections Manager](https://nestservices.google.com/partnerconnections)): If you are then still not seeing events, it's possible you need to adjust the Google Home App settings. Refer to the [Google Home App Notification Settings](#google-home-app-notification-settings) for details.
+
+- **Configuration error: Failed to create subscriber `subscription/name` was not found** - By default, Google pub/sub subscriptions will be deleted after 31 days of inactivity ([reference](https://cloud.google.com/knowledge/kb/pub-sub-subscriptions-disappeared-without-any-deletion-logs-000004170)). If this happens, then the integration will fail, and you will see the preceding log line in your Home Assistant logs. If that is the case, then:
+
+  1. Go to the [Device Access Console](https://console.nest.google.com/device-access/project-list) and re-enable the Pub/Sub Topic.
+  2. The Nest integration may need to be recreated to pick up the new Pub/Sub topic.
+  3. (Optional) To prevent future expirations, go to your [Google Cloud Console Pub/Sub subscription page](https://console.cloud.google.com/cloudpubsub/subscription/list) and edit the Pub/Sub subscription created by Nest to not expire by default.
diff --git a/source/_integrations/squeezebox.markdown b/source/_integrations/squeezebox.markdown
index d9cc0b10305..7be7a9d6ed8 100644
--- a/source/_integrations/squeezebox.markdown
+++ b/source/_integrations/squeezebox.markdown
@@ -21,7 +21,7 @@ ha_integration_type: integration
 
 The Squeezebox integration allows you to control music players from the [Lyrion Music Server](https://lyrion.org/) (LMS) ecosystem.  Lyrion Music Server was formerly known as [Logitech Media Server](https://en.wikipedia.org/wiki/Squeezebox_%28network_music_player%29).
 
-This integration provides both media players connected to the server and supporting binary sensors for the server status.
+This integration connects to an existing <abbr title="Lyrion Music Server">LMS</abbr> server and provides both media players and sensors for monitoring server status.
 
 The Squeezebox music player ecosystem, which can be controlled through this integration, includes hardware audio players from Logitech, including [Squeezebox 3rd Generation, Squeezebox Boom, Squeezebox Receiver, Transporter, Squeezebox2, Squeezebox and SLIMP3](https://lms-community.github.io/players-and-controllers/hardware-comparison/), and many software emulators like [Squeezelite, SqueezeSlave, SoftSqueeze and SqueezePlay](https://sourceforge.net/projects/lmsclients/files/).
 
diff --git a/source/_integrations/weather.markdown b/source/_integrations/weather.markdown
index e04d50e2075..b42df01bff5 100644
--- a/source/_integrations/weather.markdown
+++ b/source/_integrations/weather.markdown
@@ -33,7 +33,7 @@ The `weather` {% term entity %} can provide the conditions listed below as its s
 - **Cloudy**: There are many clouds in the sky. `cloudy`.
 - **Fog**: There is a thick mist or fog reducing visibility. `fog`.
 - **Hail**: Hailstones are falling. `hail`.
-- **Lightning**: Lightning/thunderstorms are occurring. `lighting`.
+- **Lightning**: Lightning/thunderstorms are occurring. `lightning`.
 - **Lightning, rainy**: Lightning/thunderstorm is occurring along with rain. `lightning-rainy`.
 - **Partly cloudy**: The sky is partially covered with clouds. `partlycloudy`.
 - **Pouring**: It is raining heavily. `pouring`.