Rename Services to Actions: URL Fixes (#33844)

source/_docs/scripts/service-calls.markdown

@@ -57,7 +57,7 @@ data:
   rgb_color: [255, 0, 0]
 ```
 
-A full list of the parameters for an action can be found on the documentation page of each integration, in the same way as it's done for the `light.turn_on` [action](/integrations/light/#service-lightturn_on).
+A full list of the parameters for an action can be found on the documentation page of each integration, in the same way as it's done for the `light.turn_on` [action](/integrations/light/#action-lightturn_on).
 
 ### Use templates to decide which action to perform
 
@@ -184,10 +184,10 @@ There are four `homeassistant` actions that aren't tied to any single domain, th
 - `homeassistant.toggle` - Turns off an entity that is on, or turns on an entity that is off (that supports being turned on and off)
 - `homeassistant.update_entity` - Request the update of an entity, rather than waiting for the next scheduled update, for example [Google travel time] sensor, a [template sensor], or a [light]
 
-Complete action details and examples can be found on the [Home Assistant integration][homeassistant-integration-services] page.
+Complete action details and examples can be found on the [Home Assistant integration][homeassistant-integration-actions] page.
 
 [templating]: /docs/configuration/templating/
 [google travel time]: /integrations/google_travel_time/
 [template sensor]: /integrations/template/
 [light]: /integrations/light/
-[homeassistant-integration-services]: /integrations/homeassistant#services
+[homeassistant-integration-actions]: /integrations/homeassistant#actions

source/_includes/asides/docs_sitemap.html

@@ -259,7 +259,7 @@
     <li>{% active_link /integrations/mqtt/#broker-configuration Broker %}</li>
     <li>{% active_link /integrations/mqtt/#advanced-broker-configuration Certificate %}</li>
     <li>{% active_link /integrations/mqtt/#mqtt-discovery Discovery %}</li>
-    <li>{% active_link /integrations/mqtt/#publish--dump-services Publish service %}</li>
+    <li>{% active_link /integrations/mqtt/#publish--dump-actions Publish action %}</li>
     <li>{% active_link /integrations/mqtt/#birth-and-last-will-messages Birth and last will messages %}</li>
     <li>{% active_link /integrations/mqtt/#testing-your-setup Testing your setup %}</li>
     <li>{% active_link /integrations/mqtt/#logging Logging %}</li>

source/_redirects

@@ -310,7 +310,7 @@ layout: null
 /docs/z-wave/events /integrations/zwave_js#events
 /docs/z-wave/installation /integrations/zwave_js#configuration
 /docs/z-wave/query-stage /integrations/zwave_js
-/docs/z-wave/services /integrations/zwave_js#services
+/docs/z-wave/services /integrations/zwave_js#actions
 /ecosystem/ios/notifications https://companion.home-assistant.io/docs/notifications/notifications-basic
 /ecosystem/notebooks https://data.home-assistant.io
 /ecosystem/notebooks/api https://data.home-assistant.io

source/more-info/free-space.markdown

@@ -2,7 +2,7 @@
 title: "Clear up storage"
 description: "More information on how to clear up storage in Home Assistant."
 related:
-  - docs: /integrations/recorder/#service-purge
+  - docs: /integrations/recorder/#action-purge
     title: purge the contents of the database
   - docs: /common-tasks/os/#network-storage
     title: Add network storage
@@ -25,7 +25,7 @@ There are several things you can do to free up some space:
 
 The Home Assistant database can get huge!
 
-Luckily, there is a tool you can use to [purge the contents of the database](/integrations/recorder/#service-purge)
+Luckily, there is a tool you can use to [purge the contents of the database](/integrations/recorder/#action-purge)
 
 You can [filter](/integrations/recorder/#configure-filter) what you send to
 the database, and even change how long it stores the data