diff --git a/content/ember/v3/handler-infos.md b/content/ember/v3/handler-infos.md
new file mode 100644
index 000000000..550f6b9b4
--- /dev/null
+++ b/content/ember/v3/handler-infos.md
@@ -0,0 +1,44 @@
+---
+id: remove-handler-infos
+title: HandlerInfos Removal
+until: '3.9.0'
+since: '3.6'
+---
+
+`HandlerInfo` was a private API that has been renamed to `RouteInfo` to align with the [router service RFC](https://github.com/emberjs/rfcs/blob/master/text/0095-router-service.md). If you need access to information about the routes, you are probably better served injecting the router service as it exposes a publically supported version of the `RouteInfo`s. You can access them in the following ways:
+
+```javascript
+import Route from '@ember/routing/route';
+import { inject as service } from '@ember/service';
+
+export default Route.extend({
+  router: service(),
+  init() {
+    this._super(...arguments);
+    this.router.on('routeWillChange', transition => {
+      let { to: toRouteInfo, from: fromRouteInfo } = transition;
+      console.log(`Transitioning from -> ${fromRouteInfo.name}`);
+      console.log(`to -> ${toRouteInfo.name}`);
+    });
+
+    this.router.on('routeDidChange', transition => {
+      let { to: toRouteInfo, from: fromRouteInfo } = transition;
+      console.log(`Transitioned from -> ${fromRouteInfo.name}`);
+      console.log(`to -> ${toRouteInfo.name}`);
+    });
+  }
+
+  actions: {
+    sendAnaltics() {
+      let routeInfo = this.router.currentRoute;
+      ga.send('pageView', {
+        pageName: routeInfo.name,
+        metaData: {
+          queryParams: routeInfo.queryParams,
+          params: routeInfo.params,
+        }
+      });
+    }
+  }
+});
+```
\ No newline at end of file
diff --git a/content/ember/v3/router-events.md b/content/ember/v3/router-events.md
new file mode 100644
index 000000000..d0e9a9d03
--- /dev/null
+++ b/content/ember/v3/router-events.md
@@ -0,0 +1,120 @@
+---
+id: deprecate-router-events
+title: Deprecate Router Events
+until: '4.0.0'
+since: '3.6'
+---
+
+Application-wide transition monitoring events belong on the Router service, not spread throughout the Route classes. That is the reason for the existing `willTransition` and `didTransition` hooks/events on the Router. But they are not sufficient to capture all the detail people need.
+
+In addition, they receive handlerInfos in their arguments, which are an undocumented internal implementation detail of router.js that doesn't belong in Ember's public API. Everything you can do with handlerInfos can be done with the `RouteInfo`.
+
+Below is how you would transition both the `Route` and `Router` usages of `willTransition` and `didTransition`.
+
+### Route
+
+From:
+
+```javascript
+import Route from '@ember/routing/route';
+
+export default Route.extend({
+  actions: {
+    willTransition(transition) {
+      if (this.controller.get('userHasEnteredData') &&
+          !confirm('Are you sure you want to abandon progress?')) {
+        transition.abort();
+      } else {
+        // Bubble the `willTransition` action so that
+        // parent routes can decide whether or not to abort.
+        return true;
+      }
+    },
+
+    didTransition() {
+      this.controller.get('errors.base').clear();
+      return true; // Bubble the didTransition event
+    }
+  }
+});
+```
+
+To:
+
+```js
+import Route from '@ember/routing/route';
+import { inject as service } from '@ember/service';
+
+export default Route.extend({
+  router: service(),
+  init() {
+    this.router.on('routeWillChange', transition => {
+      if (this.controller.get('userHasEnteredData') &&
+          !confirm('Are you sure you want to abandon progress?')) {
+        transition.abort();
+      }
+
+      // No need to return, no longer in a bubbling API
+    });
+
+    this.router.on('routeDidChange', transition => {
+      this.controller.get('errors.base').clear();
+      // No need to return, no longer in a bubbling API
+    });
+  }
+```
+
+### Router
+
+From:
+
+```js
+import Router from '@ember/routing/router';
+import { inject as service } from '@ember/service';
+
+export default Router.extend({
+  currentUser: service('current-user'),
+
+  willTransition(transition) {
+    this._super(...arguments);
+    if (!this.currentUser.isLoggedIn) {
+      transition.abort();
+      this.transitionTo('login');
+    }
+  },
+
+  didTransition(privateInfos) {
+    this._super(...arguments);
+    ga.send('pageView', {
+      pageName: privateInfos.name
+    });
+  }
+});
+```
+
+To:
+
+```js
+import Router from '@ember/routing/router';
+import { inject as service } from '@ember/service';
+
+export default Router.extend({
+  currentUser: service('current-user'),
+
+  init() {
+    this._super(...arguments);
+    this.on('routeWillChange', transition => {
+      if (!this.currentUser.isLoggedIn) {
+        transition.abort();
+        this.transitionTo('login');
+      }
+    });
+
+    this.on('routeDidChange', transition => {
+      ga.send('pageView', {
+        pageName: transition.to.name
+      });
+    });
+  }
+});
+```
\ No newline at end of file
diff --git a/content/ember/v3/transition-state.md b/content/ember/v3/transition-state.md
new file mode 100644
index 000000000..cea40fc4e
--- /dev/null
+++ b/content/ember/v3/transition-state.md
@@ -0,0 +1,56 @@
+---
+id: transition-state
+title: Transition State Removal
+until: '3.9.0'
+since: '3.6'
+---
+
+The `Transition` object is a public interface that actually exposed internal state used by router.js to perform routing. Accessing `state`, `queryParams` or `params` on the `Transition` has been removed. If you need access to information about the routes, you are probably better served injecting the router service as it exposes a publically supported version of the `RouteInfo`s. You can access them in the following ways:
+
+```javascript
+import Route from '@ember/routing/route';
+import { inject as service } from '@ember/service';
+
+export default Route.extend({
+  router: service(),
+  init() {
+    this._super(...arguments);
+    this.router.on('routeWillChange', transition => {
+      let { to: toRouteInfo, from: fromRouteInfo } = transition;
+      console.log(`Transitioning from -> ${fromRouteInfo.name}`);
+      console.log(`From QPs: ${JSON.stringify(fromRouteInfo.queryParams)}`);
+      console.log(`From Params: ${JSON.stringify(fromRouteInfo.params)}`);
+      console.log(`From ParamNames: ${fromRouteInfo.paramNames.join(', ')}`);
+      console.log(`to -> ${toRouteInfo.name}`);
+      console.log(`To QPs: ${JSON.stringify(toRouteInfo.queryParams)}`);
+      console.log(`To Params: ${JSON.stringify(toRouteInfo.params)}`);
+      console.log(`To ParamNames: ${toRouteInfo.paramNames.join(', ')}`);
+    });
+
+    this.router.on('routeDidChange', transition => {
+      let { to: toRouteInfo, from: fromRouteInfo } = transition;
+      console.log(`Transitioned from -> ${fromRouteInfo.name}`);
+      console.log(`From QPs: ${JSON.stringify(fromRouteInfo.queryParams)}`);
+      console.log(`From Params: ${JSON.stringify(fromRouteInfo.params)}`);
+      console.log(`From ParamNames: ${fromRouteInfo.paramNames.join(', ')}`);
+      console.log(`to -> ${toRouteInfo.name}`);
+      console.log(`To QPs: ${JSON.stringify(toRouteInfo.queryParams)}`);
+      console.log(`To Params: ${JSON.stringify(toRouteInfo.params)}`);
+      console.log(`To ParamNames: ${toRouteInfo.paramNames.join(', ')}`);
+    });
+  }
+
+  actions: {
+    sendAnaltics() {
+      let routeInfo = this.router.currentRoute;
+      ga.send('pageView', {
+        pageName: routeInfo.name,
+        metaData: {
+          queryParams: routeInfo.queryParams,
+          params: routeInfo.params,
+        }
+      });
+    }
+  }
+});
+```
\ No newline at end of file