Merge pull request ember-learn#632 from ember-learn/jet-fuel

Fix failing links, markdown linting, and spelling errors

Author: MelSumner

.local.dic

@@ -1,5 +1,7 @@
 30KB
 accessor
+accessors
+Accessors
 activations
 acyclic
 ActiveSupport
@@ -8,6 +10,7 @@ Americentric
 assistive
 asynchrony
 autocomplete
+autotrack
 auto-rollup
 autoruns
 backend
@@ -19,11 +22,15 @@ breakpoint
 Browserlist
 camelize
 chainable
+cheatsheet
 Checkboxes
 checkboxes
 CoffeeScript
 componentized
+composable
 Ctrl-C
+customizable
+Customizable
 customizations
 D3
 dasherize
@@ -49,11 +56,15 @@ Evented
 facto
 falsy
 focusable
+foundational
 frontend
 fullname
 geocode
 geocoding
 Geolocation
+getter
+getters
+Getters
 globbing
 *google
 HammerJS
@@ -69,9 +80,11 @@ Inflector
 instantiation
 jquery-integration
 keyCode
+KVO
 linters
 lookups
 Mapbox
+MDN
 mixin
 mixins
 modularity
@@ -85,16 +98,22 @@ param
 params
 PascalCased
 pipelining
+POJO
+POJOs
 Polymorphism
 polymorphism
 PR
 PRs
 preload
 prepend
+prepended
+presentational
+Presentational
 pre-transition
 readme
 readonly
 recognizers
+Redux
 relayout
 repo
 rerender
@@ -109,24 +128,35 @@ serializers
 singularize
 SSR
 stateful
+subclasses
 subclassing
 subdomain
 subexpression
 suboptimal
 substate
 substates
+synergistically
 syntaxes
+tagless
 TalkBack
 teardown
 templating
 todo
 todos
+tooltip
+trackable
+Trackable
+Treeshaking
+truthy
 typeahead
 UIs
 unsilence
 untrusted
 usecase
 viewport
+VM
 VoiceOver
 WAI-ARIA
 WCAG
+websocket
+Websockets

guides/release/anatomy-of-an-app/index.md

@@ -1 +1 @@
-Coming soon!
+Coming soon!

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/arguments-and-attributes.md

@@ -64,7 +64,7 @@ standard identifier can:
 ```
 
 You can pass strings as arguments to components, or you can pass literal values
-using double curlies:
+using double curly brackets:
 
 ```handlebars
 <Tooltip
@@ -74,7 +74,7 @@ using double curlies:
 />
 ```
 
-Note that if you do _not_ wrap literal values in double curlies, they are
+Note that if you do _not_ wrap literal values in double curly brackets, they are
 treated as strings, like standard HTML attributes:
 
 ```handlebars
@@ -216,7 +216,7 @@ not be applied.
 
 The positioning of `...attributes` matters, with respect to the other attributes
 in the element it is applied to. Attributes that come _before_ `...attributes`
-can be overriden, but attributes that come _after_ cannot:
+can be overridden, but attributes that come _after_ cannot:
 
 ```handlebars
 <p

guides/release/components/component-basics.md

@@ -1,12 +1,12 @@
 Components are an essential building block in Ember applications. They allow
-developers to package presentation and behaviour into a single unit and give it
+developers to package presentation and behavior into a single unit and give it
 a name. You can think of them like defining your own custom HTML elements, like
 a custom `<input>` or `<select>` tag that has its own behavior, values, and
 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}
@@ -92,9 +92,9 @@ component template:
 This allows you to have some logic in your templates, and to nest components
 within each other, building up a component _tree_. The component tree in Ember
 applications is similar to the DOM tree in the HTML - in fact, you can even
-inspect it using the Ember Inspector:
+inspect it using the [Ember Inspector](../../ember-inspector/).
 
-[TODO: Screenshot of the Component tree in the Ember Inspector]
+<!-- [TODO: Screenshot of the Component tree in the Ember Inspector] -->
 
 Components can also have blocks and children, just like standard HTML elements.
 We could update the `HelloButton` component to render its button text from its

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

@@ -17,7 +17,7 @@ And to use a named argument you prefix it with `@`, like so:
 Since properties and named arguments are visually different,
 this syntax allows you to know where a value comes from when you are reading the template.
 If you encounter the `{{this.name}}` syntax,
-you know you should check the the JavaScript file of the component.
+you know you should check the JavaScript file of the component.
 If you encounter the `{{@friend}}` syntax,
 you know that the value is passed to the component when it is used in another template.
 
@@ -26,7 +26,7 @@ you know that the value is passed to the component when it is used in another te
 To display a component property in the template, you prefix it with `this`,
 like you would in JavaScript.
 
-For the example, we will build a `Greeting` component with an hard-coded name.
+For the example, we will build a `Greeting` component with a hard-coded name.
 Then, we will use that property in the component template:
 
 ```javascript {data-filename=src/ui/components/greeting/component.js}
@@ -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/glimmer-components-dom.md

@@ -1,4 +1,4 @@
-For the most part, you should be be able to build Ember applications without directly manipulating the DOM. Before considering directly accessing the DOM, it's always best to first consider whether there's an Ember-native way to accomplish your goal.
+For the most part, you should be able to build Ember applications without directly manipulating the DOM. Before considering directly accessing the DOM, it's always best to first consider whether there's an Ember-native way to accomplish your goal.
 
 ## Thinking About Updates
 
@@ -159,7 +159,7 @@ export default class Counter extends Component {
     <div class="cta-note-body">
       <div class="cta-note-heading">Tomster says...</div>
       <div class="cta-note-message">
-        "Element modifiers" appear inside free-floating curlies inside of an opening
+        "Element modifiers" appear inside free-floating curly brackets inside of an opening
         tag. Unlike <strong>attribute syntax</strong>, which works by substitution
         (and therefore affects the HTML output of your page), element modifiers work
         by passing the element to a function that can do anything with it.

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/controllers/index.md

@@ -71,7 +71,7 @@ export default Controller.extend({
 });
 ```
 
-The property `isExpanded` keeps track if the user has expanded the body or not. The action `toggleBody()` provides a way for the user to provide their setting. Both of the them are used in the updated template below.
+The property `isExpanded` keeps track if the user has expanded the body or not. The action `toggleBody()` provides a way for the user to provide their setting. Both of them are used in the updated template below.
 
 ```handlebars {data-filename=app/templates/blog-post.hbs}
 <h1>{{this.model.title}}</h1>

guides/release/data-management/index.md

@@ -1 +1 @@
-Coming soon!
+Coming soon!

guides/release/deploying/index.md

@@ -1 +1 @@
-Coming soon!
+Coming soon!

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,9 +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