fixing all image links (because of new trailing slash issue) (#16)

Author: mansona

.gitignore

@@ -1 +1,2 @@
 .DS_Store
+node_modules

guides/v1.12.0/ember-inspector/troubleshooting.md

@@ -8,7 +8,7 @@ If the inspector cannot detect an Ember application, you will see
 the following message:
 
 <img
-src="../../images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
+src="/images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
 
 Some of the reasons this happens:
 

guides/v1.13.0/ember-inspector/troubleshooting.md

@@ -8,7 +8,7 @@ If the inspector cannot detect an Ember application, you will see
 the following message:
 
 <img
-src="../../images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
+src="/images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
 
 Some of the reasons this happens:
 

guides/v2.0.0/ember-inspector/troubleshooting.md

@@ -8,7 +8,7 @@ If the Inspector cannot detect an Ember application, you will see
 the following message:
 
 <img
-src="../../images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
+src="/images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
 
 Some of the reasons this may happen:
 

guides/v2.1.0/ember-inspector/troubleshooting.md

@@ -8,7 +8,7 @@ If the Inspector cannot detect an Ember application, you will see
 the following message:
 
 <img
-src="../../images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
+src="/images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
 
 Some of the reasons this may happen:
 

guides/v2.10.0/configuring-ember/handling-deprecations.md

@@ -3,7 +3,7 @@ changes to the framework.  Before any functionality or API is removed it first g
 still supported, but usage of it generates a warning logged to the browser console.  These warnings can pile up between major releases to a point where the amount of
 deprecation warnings that scroll through the console becomes overwhelming.
 
-<img width="675px" title="Deprecations Clouding up the Browser JavaScript Console" src="../../images/guides/configuring-ember/handling-deprecations/deprecations-in-console.png"/>
+<img width="675px" title="Deprecations Clouding up the Browser JavaScript Console" src="/images/guides/configuring-ember/handling-deprecations/deprecations-in-console.png"/>
 
 Fortunately, Ember provides a way for projects to deal with deprecations in an organized and efficient manner.
 
@@ -47,7 +47,7 @@ manually exercise functionality within your app where needed.  Once you've exerc
 your browser console: `deprecationWorkflow.flushDeprecations()`.  This will print to the console JavaScript code, which you should then copy to a
 new file in your project called `/config/deprecation-workflow.js`
 
-<img width="675px" title="Generated Deprecation Code from Browser Console" src="../../images/guides/configuring-ember/handling-deprecations/generate-deprecation-code.png"/>
+<img width="675px" title="Generated Deprecation Code from Browser Console" src="/images/guides/configuring-ember/handling-deprecations/generate-deprecation-code.png"/>
 
 Here's an example of a deprecation-workflow file after generated from the console:
 
@@ -108,7 +108,7 @@ window.deprecationWorkflow.config = {
   ]
 };
 ```
-<img width="675px" src="../../images/guides/configuring-ember/handling-deprecations/failed-test-from-deprecation.png"/>
+<img width="675px" src="/images/guides/configuring-ember/handling-deprecations/failed-test-from-deprecation.png"/>
 
 
 ### 3. Fix and Repeat
@@ -125,7 +125,7 @@ so that you can start the process over for the next release.
 As you upgrade between releases, you might also notice that your terminal log begins to stream template-related deprecation warnings during the compile process, making
 it difficult to review your compilation logs.
 
-<img width="675px" src="../../images/guides/configuring-ember/handling-deprecations/compile-deprecations.png" title="Compile Deprecations Clouding Log"/>
+<img width="675px" src="/images/guides/configuring-ember/handling-deprecations/compile-deprecations.png" title="Compile Deprecations Clouding Log"/>
 
 If you are using the deprecation workflow process above, you will likely prefer to gather these warnings during runtime execution instead.  The way to hide these
 warnings during compile is to install the [ember-cli-template-lint](http://emberobserver.com/addons/ember-cli-template-lint) addon.  It suppresses

guides/v2.10.0/ember-inspector/troubleshooting.md

@@ -8,7 +8,7 @@ If the Inspector cannot detect an Ember application, you will see
 the following message:
 
 <img
-src="../../images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
+src="/images/guides/ember-inspector/troubleshooting-application-not-detected.png" width="350">
 
 Some of the reasons this may happen:
 

guides/v2.10.0/getting-started/core-concepts.md

@@ -1,7 +1,7 @@
 Before you start writing any Ember code, it's a good idea to get an overview of how an
 Ember application works.
 
-![ember core concepts](../../images/ember-core-concepts/ember-core-concepts.png)
+![ember core concepts](/images/ember-core-concepts/ember-core-concepts.png)
 
 ## Router and Route Handlers
 Imagine we are writing a web app for a site that lets users list their properties to rent. At any given time, we should be able to answer questions about the current state like _What rental are they looking at?_ and _Are they editing it?_ In Ember, the answer to these questions is determined by the URL.

guides/v2.10.0/tutorial/acceptance-test.md

@@ -3,7 +3,7 @@ It will start with a homepage, an about page and a contact page.
 
 Here's a look at the desired application before we get started.
 
-![super rentals homepage screenshot](../../images/service/style-super-rentals-maps.png)
+![super rentals homepage screenshot](/images/service/style-super-rentals-maps.png)
 
 Let's think through what we want to do on the home page of our Super Rentals application.
 
@@ -178,7 +178,7 @@ test('should show details for a specific rental', function (assert) {
 Of course because we have not implemented this functionality yet, our tests will all fail.
 So, your test output should now show all failed tests when running `ember test --server`, which gives us a todo list for the rest of the tutorial.
 
-![failing tests](../../images/acceptance-test/failed-acceptance-tests.png)
+![failing tests](/images/acceptance-test/failed-acceptance-tests.png)
 
 As we walk through the tutorial, we'll use our acceptance tests as a checklist of functionality.
 When all are green, we've accomplished our high level goals!

guides/v2.10.0/tutorial/autocomplete-component.md

@@ -262,6 +262,6 @@ export default function() {
 
 After updating our mirage configuration, we should see passing tests, as well as a simple filter on your home screen, that will update the rental list as you type:
 
-![home screen with filter component](../../images/autocomplete-component/styled-super-rentals-filter.png)
+![home screen with filter component](/images/autocomplete-component/styled-super-rentals-filter.png)
 
-![passing acceptance tests](../../images/autocomplete-component/passing-acceptance-tests.png)
+![passing acceptance tests](/images/autocomplete-component/passing-acceptance-tests.png)