fix broken links

Author: jenweber

guides/release/components/actions-and-events.md

@@ -54,7 +54,7 @@ confirmation that will show conditionally based on its `showConfirmation`
 property. You'll notice this property is decorated with the `@tracked`
 decorator - this is known as a _tracked property_, and indicates to Ember that
 the field will change in value over time. We'll discuss this more in the section
-on [State Management](../../state-management).
+on [State Management](../../state-management/).
 
 Next, we need to hook up the button to toggle that property. We'll
 do this with an _action_:
@@ -168,7 +168,7 @@ then confirms. In the first case, we'll find the user's account and delete it.
 
 We'll implement an action on the parent component called
 `userDidDeleteAccount()` that, when called, gets a hypothetical `login`
-[service](../../applications/services/) and calls the service's `deleteUser()`
+[service](../../services/) and calls the service's `deleteUser()`
 method. We'll go over services later on - for now, think of it as an API
 that manages the user's login and information.
 

guides/release/components/component-basics.md

@@ -6,7 +6,7 @@ events that you can hook into in your templates. However, they shouldn't be
 confused with [_web components_](https://www.webcomponents.org/), which are a
 browser based API that is similar, but not as powerful as Ember components.
 
-Like we mentioned in the section on [Templates](../../templates/), components
+Like we mentioned in the section on [Templates](../../templates/handlebars-basics/), components
 can have both a template and a class definition, like so:
 
 ```handlebars {data-filename=app/templates/components/hello-button.hbs}

guides/release/components/defining-a-component.md

@@ -76,7 +76,7 @@ will be covered later on in the guides.
 ### Component Templates
 
 Templates in components use the Handlebars templating language, as discussed in
-the [Templating](../../templating) section. A component's template is the layout
+the [Templating](../../templates/handlebars-basics/) section. A component's template is the layout
 that is used when rendering the component. If we update the `BlogPost`'s
 template to be:
 
@@ -127,7 +127,7 @@ Here, we have two different kinds of dynamic values:
   ```
 
   We'll talk more about arguments in [the next
-  section](../arguments-and-attributes). All arguments are prefixed with the `@`
+  section](../arguments-and-attributes/). All arguments are prefixed with the `@`
   symbol, so whenever you see `{{@...` you know its referring to any argument.
 
 - `{{this.sectionClass}}` refers to a _property_ of the component _instance_.
@@ -148,9 +148,10 @@ class property for title or post content:
 </section>
 ```
 
-Both arguments and properties can be used in any valid binding location (for
-more details on where and how you can bind values, read through the [section on
-templating](../../templating)). The reason you would choose an argument or
+Both arguments and properties can be used in any valid binding location. For
+more details on where and how you can bind values, read through the
+[section on templating](../../templates/handlebars-basics/).
+The reason you would choose an argument or
 property is based on how you expect to use the component, and whether or not the
 value should be based on internal logic within the component, or values passed
 to the component where it is used.
@@ -179,7 +180,7 @@ templates, and to nest components within each other, building up a component
 _tree_.
 
 Finally, component templates can use a special helper: `{{yield}}`. We'll cover
-this helper in more detail in the [Yields](../yields) section later on, but this
+this helper in more detail in the [Yields](../yields/) section later on, but this
 helper allows us to specify that users can pass the component a _block_ of
 children, and where those children should be placed. If we go back to our
 `BlogPost` component, we can add a yield like this:
@@ -233,7 +234,7 @@ placed on any HTML element or component within the component's template:
 ```
 
 We'll talk more about attributes in [the next
-section](../arguments-and-attributes). They are values that get applied directly
+section](../arguments-and-attributes/). They are values that get applied directly
 to elements, and can be used to customize the HTML of a component. Unlike
 arguments, they are _not_ prefixed with the `@` symbol:
 

guides/release/components/displaying-data.md

@@ -96,4 +96,4 @@ The output will be:
 <p>Hello Zoey, I'm Tomster!</p>
 ```
 
-For more detailed information see [Passing arguments and HTML attributes](./passing-arguments-and-html-attributes).
+For more detailed information see [Passing arguments and HTML attributes](./arguments-and-attributes).

guides/release/components/wrapping-content-in-a-component.md

@@ -13,7 +13,9 @@ Now, we can use the `<BlogPost />` component and pass it properties in another t
 <BlogPost @title={{this.title}} @body={{this.body}} />
 ```
 
-See [Passing Properties to a Component](../passing-arguments-and-html-attributes/) for more.
+See 
+[Passing Properties to a Component](../arguments-and-attributes/)
+for more.
 
 In this case, the content we wanted to display came from the model.
 But what if we want the developer using our component to be able to provide custom HTML content?

guides/release/getting-started/core-concepts.md

@@ -66,7 +66,7 @@ In Ember, we use the term **hook** for methods that are automatically called wit
 
 Some examples of a hook are:
 
-* [Component Lifecycle Hooks](../../components/the-component-lifecycle/): the [`willRender()`](https://emberjs.com/api/ember/release/classes/Component/methods/willRender?anchor=willRender/) hook gets called before each time a component renders
+* [Component Lifecycle Hooks](../../components/glimmer-components-dom/): the [`willRender()`](https://emberjs.com/api/ember/release/classes/Component/methods/willRender?anchor=willRender/) hook gets called before each time a component renders
 * Route Hooks: the [`model()`](https://www.emberjs.com/api/ember/release/classes/Route/methods/model?anchor=model/) hook is used to load the model on a route
 
 In the following example, the [`didRender()`](https://emberjs.com/api/ember/release/classes/Component/methods?anchor=didRender/) component lifecycle hook is used to log "I rendered!" to the console after each time the component is rendered.

guides/release/pages.yml

@@ -109,8 +109,9 @@
 - title: "Services"
   url: "services"
   pages:
-    - title: Introduction
-      url: "services"
+    - title: Overview
+      url: "index"
+      
 - title: 'Data Management'
   url: 'data-management'
   pages:

guides/release/reference/syntax-conversion-guide.md

@@ -61,7 +61,7 @@ In the following example, `"greeting"` and `"name"` are positional parameters:
 {{my-greeting "Hello" "World"}}
 ```
 
-As shown in the relevant ["Position Params"](../../components/passing-arguments-and-html-attributes/#toc_positional-params) part of the Guides,
+As shown in the relevant ["Position Params"](../../components/arguments-and-attributes/#toc_positional-params) part of the Guides,
 there are two ways to handle them inside the component.
 One way is to individually specify what component property the positional parameter should map to.
 The other way is to map all positional parameters to the `params` property and refer to them by their index.

guides/release/routing/redirection.md

@@ -49,7 +49,7 @@ See [Storing and Retrying a Transition](../preventing-and-retrying-transitions/#
 for how to do that.
 
 If you need to examine some application state to figure out where to redirect,
-you might use a [service](../../applications/services/).
+you might use a [service](../../services/).
 
 ## Transitioning After the Model is Known
 

guides/release/services/services.md renamed to guides/release/services/index.md

@@ -59,9 +59,6 @@ Which will render the following HTML:
 </a>
 ```
 
-Components can control which of their elements receive attributes.
-[Read more about how to customize a component's element](../../components/customizing-a-components-element/).
-
 <div class="cta">
   <div class="cta-note">
     <div class="cta-note-body">

guides/release/templates/binding-element-attributes.md

@@ -51,7 +51,7 @@ ember generate route my-route-name
 A typical, modern web app is made of dozens of files that have to all be combined together into something the browser can understand.
 Ember does this work for you with zero configuration, but as a result, there are some rules to follow when it comes to adding assets into your HTML.
 
-You cannot use script tags directly within a template, and should use [actions](../actions/) or [Component Lifecycle Hooks](../../components/the-component-lifecycle/) to make your app responsive to user interactions and new data.
+You cannot use script tags directly within a template, and should use [actions](../actions/) or [Component Lifecycle Hooks](../../components/glimmer-components-dom/) to make your app responsive to user interactions and new data.
 If you are working with a non-Ember JavaScript library and need to use a `js` file from it, see the Guide section [Addons and Dependencies](../../addons-and-dependencies/managing-dependencies/).
 
 You should not add links to your own local CSS files within the `hbs` file.

guides/release/templates/handlebars-basics.md

@@ -105,7 +105,7 @@ export default class ListFilterComponent extends Component {
 In the above example we use the `init` hook to seed our initial listings by calling the `filter` action with an empty value.
 Our `handleFilterEntry` action calls a function called `filter` based on the `value` attribute set by the input helper.
 
-The `filter` function is passed in by the calling object. This is a pattern known as [closure actions](../../components/adding-actions/#toc_passing-the-action-to-the-component).
+The `filter` function is passed in by the calling object. This is a pattern known as closure actions.
 
 Notice the `then` function called on the result of calling the `filter` function.
 The code expects the `filter` function to return a promise.

guides/release/tutorial/autocomplete-component.md

@@ -1,5 +1,5 @@
 For Super Rentals, we want to be able to display a map showing where each rental is.
-We will use an [Ember service](../../applications/services/) to implement this feature.
+We will use an [Ember service](../../services/) to implement this feature.
 
 We plan to use the following services to provide maps.
 
@@ -54,7 +54,7 @@ we will implement a map element service that will create an HTML `div` element a
 The service will also keep a reference to the element we create,
 so that a map for a given location will only have to be generated once.
 
-Accessing our maps API through a [service](../../applications/services/) will give us several benefits:
+Accessing our maps API through a [service](../../services/) will give us several benefits:
 
 * It is injected with a [service locator](https://en.wikipedia.org/wiki/Service_locator_pattern),
   meaning it will abstract the maps API from the code that uses it,
@@ -133,13 +133,13 @@ ember g component location-map
 Running this command generates three files: a component JavaScript file, a template, and a test file.
 
 We provide the maps service into our component by initializing a property of our component, called `mapElement`.
-Services are commonly made available in components and other Ember objects by ["service injection"](../../applications/services/#toc_accessing-services).
+Services are commonly made available in components and other Ember objects by ["service injection"](../../services/#toc_accessing-services).
 When you initialize a property with `import { inject } from '@ember/service';`,
 Ember tries to set that property with a service matching its name.
 
 With our `mapElement` service, our component will call the `getMapElement` function with the provided location.
 We append the map element we get back from the service by implementing `didInsertElement`,
-which is a [component lifecycle hook](../../components/the-component-lifecycle/#toc_integrating-with-third-party-libraries-with-didinsertelement).
+which is a [component lifecycle hook](../../components/glimmer-components-dom/#toc_integrating-with-third-party-libraries-with-didinsertelement).
 This function runs during the component render, after the component's markup gets inserted into the page.
 
 ```javascript {data-filename="app/components/location-map.js" data-diff="+2,+5,+6,+7,+9,+10,+11,+12,+13,+14"}

guides/release/tutorial/service.md

@@ -225,7 +225,7 @@ Move on to the [next page](../hbs-helper/) for the next feature, or continue on
 
 Ember components are commonly tested with [component integration tests](../../testing/testing-components/).
 Component integration tests verify the behavior of a component within the context of Ember's rendering engine.
-When running in an integration test, the component goes through its regular [render lifecycle](../../components/the-component-lifecycle/),
+When running in an integration test, the component goes through its regular [render lifecycle](../../components/glimmer-components-dom/),
 and has access to dependent objects, loaded through Ember's resolver.
 
 Our component integration test will test two different behaviors: