apply newline and markdown link syntax linting

Author: jenweber

guides/release/components/component-basics.md

@@ -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/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](./passing-arguments-and-html-attributes).

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/state-management/patterns-for-state.md

@@ -210,12 +210,10 @@ Once the data loads, it updates the state, and data flows downward like normal
 
 Background events are similar to data loading. Something is scheduled to happen
 in the background, like a `setTimeout` or `setInterval`, a callback scheduled in
-the [run loop][2], or connection is opened to something that communicates
+the [run loop](../../applications/run-loop/), or connection is opened to something that communicates
 directly with the app, like a websocket or a web worker. When these events occur
 and update state, they trigger a rerender just like data loading.
 
-[2]:
-
 Background events and data fetching can both trigger actions as well when they
 occur in components, in which case they may interact with other components in
 the component tree:

guides/release/upgrading/deprecations.md

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

guides/release/upgrading/index.md

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

guides/release/working-with-javascript/classic-classes.md

@@ -156,10 +156,9 @@ Person.create({ name: 'Stefan Penner' }); // Stefan Penner, reporting for duty!
 
 ### Methods
 
-Methods are functions that are defined on the class using [object method
-syntax][4], and that usable by instances:
-
-[4]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Method_definitions
+Methods are functions that are defined on the class using 
+[object method syntax](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Method_definitions),
+and that usable by instances:
 
 ```js
 const Person = EmberObject.extend({
@@ -532,13 +531,12 @@ In certain cases, you will want to pass arguments to the super method before or
 after overriding. This allows the super class method to continue operating as it
 normally would.
 
-One common example is when overriding the [`normalizeResponse()`][4] hook in one
-of Ember-Data's serializers.
+One common example is when overriding the 
+[`normalizeResponse()`](https://www.emberjs.com/api/ember-data/release/classes/DS.JSONAPISerializer/methods/normalizeResponse?anchor=normalizeResponse)
+hook in one of Ember-Data's serializers.
 
 A handy shortcut for this is to use a "spread operator", like `...arguments`:
 
-[4]: https://www.emberjs.com/api/ember-data/release/classes/DS.JSONAPISerializer/methods/normalizeResponse?anchor=normalizeResponse
-
 ```javascript
 normalizeResponse(store, primaryModelClass, payload, id, requestType)  {
   // Customize my JSON payload for Ember-Data

guides/release/working-with-javascript/native-classes.md

@@ -674,13 +674,12 @@ In certain cases, you will want to pass arguments to the super method before or
 after overriding. This allows the super class method to continue operating as it
 normally would.
 
-One common example is when overriding the [`normalizeResponse()`][5] hook in one
-of Ember Data's serializers.
+One common example is when overriding the 
+[`normalizeResponse()`](https://www.emberjs.com/api/ember-data/release/classes/DS.JSONAPISerializer/methods/normalizeResponse?anchor=normalizeResponse)
+hook in one of Ember Data's serializers.
 
 A handy shortcut for this is to use a "spread operator", like `...arguments`:
 
-[5]: https://www.emberjs.com/api/ember-data/release/classes/DS.JSONAPISerializer/methods/normalizeResponse?anchor=normalizeResponse
-
 ```javascript
 normalizeResponse(store, primaryModelClass, payload, id, requestType)  {
   // Customize my JSON payload for Ember-Data

guides/v3.7.0/contributing/adding-new-features.md

@@ -161,4 +161,4 @@ Every week, we repeat the Go/No-Go process for the features that remain
 on the beta branch. Any feature that has become unready is removed from
 the `features.json`.
 
-Once this is done, a Beta release is tagged and pushed.
+Once this is done, a Beta release is tagged and pushed.