Fix Lando service links in docs

docs/getting-started.md

@@ -10,7 +10,7 @@ Before you get started with this recipe we assume that you have:
 
 1. [Installed Lando](https://docs.lando.dev/getting-started/installation.html) and gotten familiar with [its basics](https://docs.lando.dev/cli/)
 2. [Initialized](https://docs.lando.dev/cli/init.html) a [Landofile](https://docs.lando.dev/core/v3) for your codebase for use with this recipe
-3. Read about the various [services](https://docs.lando.dev/core/v3/lando-service.html), [tooling](https://docs.lando.dev/core/v3/tooling.html), [events](https://docs.lando.dev/core/v3/events.html) and [routing](https://docs.lando.dev/core/v3/proxy.html) Lando offers.
+3. Read about the various [services](https://docs.lando.dev/core/v3/services/lando.html), [tooling](https://docs.lando.dev/core/v3/tooling.html), [events](https://docs.lando.dev/core/v3/events.html) and [routing](https://docs.lando.dev/core/v3/proxy.html) Lando offers.
 
 ## Quick Start
 

docs/legacy/drupal-7.md

@@ -81,7 +81,7 @@ Because of how Lando's [php service](https://docs.lando.dev/plugins/php) sets up
 
 Said more explicitly: **if you've required `drush` via `composer` in your application then this recipe will use your `drush` and not the one you've specified in this recipes config.**
 
-If you are using a site-local Drush, it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/lando-service.html#build-steps) to automatically install Drush before your app starts up. This can prevent weird version mismatches and other issues if you are using Drush in other Lando automation like [events](https://docs.lando.dev/core/v3/events.html).
+If you are using a site-local Drush, it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) to automatically install Drush before your app starts up. This can prevent weird version mismatches and other issues if you are using Drush in other Lando automation like [events](https://docs.lando.dev/core/v3/events.html).
 
 **Automatically composer install before my app starts**
 
@@ -132,7 +132,7 @@ Make sure the alias file exists within the drush folder in your app. An example
 
 For info on how to set up your alias, please refer to the following [link](https://www.drupal.org/node/1401522) or see this [example](https://github.com/drush-ops/drush/blob/8.x/examples/example.aliases.drushrc.php).
 
-Then configure the following [build step](https://docs.lando.dev/core/v3/lando-service.html#build-steps) in your [Landofile](https://docs.lando.dev/core/v3) and `lando rebuild`.
+Then configure the following [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) in your [Landofile](https://docs.lando.dev/core/v3) and `lando rebuild`.
 
 ```yml
 services:

docs/legacy/drupal-8.md

@@ -80,7 +80,7 @@ Because of how Lando's [php service](https://docs.lando.dec/php) sets up its [`P
 
 Said more explicitly: **if you've required `drush` via `composer` in your application then this recipe will use your `drush` and not the one you've specified in this recipes config.**
 
-If you are using a site-local Drush, it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/lando-service.html#build-steps) to automatically install Drush before your app starts up. This can prevent weird version mismatches and other issues if you are using Drush in other Lando automation like [events](https://docs.lando.dev/core/v3/events.html).
+If you are using a site-local Drush, it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) to automatically install Drush before your app starts up. This can prevent weird version mismatches and other issues if you are using Drush in other Lando automation like [events](https://docs.lando.dev/core/v3/events.html).
 
 **Automatically composer install before my app starts**
 
@@ -135,7 +135,7 @@ Make sure the alias file exists within the drush folder in your app. An example
 
 For info on how to setup your alias, please refer to the following [link](https://www.drupal.org/node/1401522) or see this [example](https://raw.githubusercontent.com/drush-ops/drush/8.x/examples/example.aliases.drushrc.php).
 
-Then configure the following [build step](https://docs.lando.dev/core/v3/lando-service.html#build-steps) in your [Landofile](https://docs.lando.dev/core/v3) and `lando rebuild`.
+Then configure the following [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) in your [Landofile](https://docs.lando.dev/core/v3) and `lando rebuild`.
 
 ```yml
 services:

docs/tooling.md

@@ -55,7 +55,7 @@ Once you do, Lando will be able to use `drush` normally.
 
 #### Build steps
 
-Once `drush` is listed in your `composer.json` it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/lando-service.html#build-steps) to automatically install Drush before your app starts up. This ensures `drush` is available after `lando start` and during any other build steps or events.
+Once `drush` is listed in your `composer.json` it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) to automatically install Drush before your app starts up. This ensures `drush` is available after `lando start` and during any other build steps or events.
 
 **Automatically composer install before my app starts**