update docs

Author: patricklx

README.md

@@ -3,42 +3,11 @@
 this is based on https://github.com/discourse/ember-route-template
 but instead of creating template gts filed we use route.gts files directly.
 
-[eti]: https://github.com/ember-template-imports/ember-template-imports
 [polaris]: https://blog.emberjs.com/ember-5-0-released/#toc_the-journey-towards-ember-polaris
 [resources]: https://github.com/NullVoxPopuli/ember-resources/blob/main/docs/docs/README.md
 [rfc]: https://rfcs.emberjs.com/id/0779-first-class-component-templates/#typescript
 
-Provides an adapter for using [`<template>` tags][eti] and components in route files
-
-## Motivation
-
-So you have adopted [`<template>` tags][eti] in your app, and everything has
-been great. It's time to add a new route to the app. You created a `.gjs` file
-and programmed away, importing components and helper functions left and right,
-maybe even declaring local JavaScript helpers for use in the template.
-
-When you are done, you tested it out in the browser, and everything broke. The
-horror!
-
-Unfortunately, Ember does not support `<template>` tags as route templates at
-the moment. This is an obvious coherence gap that needs to be addressed in
-[Polaris edition][polaris], likely by doing away with the controllers and route
-templates altogether, in favor of making the route itself a component with a
-`<template>` on it, and using the [resources][resources] pattern for data
-fetching.
-
-In the meantime though, this can leave you in a tricky situation. As your app
-and your team gets deeper into the `<template>` tag paradigm, it can be awkward
-to author route templates in the old paradigm, and you may even find yourself
-having to re-export certain component/modifier/helpers from `app/` and make
-them globally available, just so they can be used in route templates.
-
-This addon bridges the gap by shipping a small adapter that turns `<template>`
-and components into the route template format Ember currently expects, so you
-can use the full feature set of `.gjs` in routes.
-
-Eventually, this addon won't be necessary anymore when the new Polaris routing
-paradigm is available.
+Provides an adapter for using [`<template>` tags] and components in route files
 
 ## Usage
 
@@ -118,15 +87,10 @@ class MyRouteComponent extends Component {
 export default RoutableComponentRoute(MyRouteComponent);
 ```
 
-With this feature, it eliminates most of the reasons for needing controllers,
-other than for query params (which is another coherence gap Polaris would need
-to address). We suggest exploring moving your non-QP controller logic into a
-component this way, treating controllers as "QP services" and nothing else.
-
 ## How it works
 
 [Under the hood](./ember-routable-component/src/index.ts), the adapter generates
-a route template that simply invokes the `<template>` or component you passed
+a route that simply invokes the `<template>` or component you passed
 in with the `@model` and `@controller` arguments appropriately set.
 
 The hello world example from above is similar to first creating the component
@@ -156,35 +120,6 @@ named exports, if you need to access them from elsewhere.
 
 TypeScript and Glint is fully supported, just use the `.gts` extension instead.
 
-One caveat is that Glint cannot automatically infer the `@model`/`@controller`
-arguments, and you will get a type error when trying to access them from the
-`<template>`, which is the usual problem you've always had with template-only
-components in Glint.
-
-According to the [RFC][rfc], you can supply a signature like this:
-
-```gts
-// app/routes/my-route.gts
-import RoutableComponentRoute from "ember-routable-component";
-
-interface MyRouteSignature {
-  Args: {
-    model: string;
-  }
-}
-
-export default RoutableComponentRoute(
-  // This does not actually work!
-  <template[MyRouteSignature]>
-    Now Glint is supposed to know {{@model}} is a string.
-  </template>
-);
-```
-
-However, as of writing, this feature was never implemented, and the Ember
-TypeScript is considering other alternatives. In the meantime, the adapter
-function can accept a controller argument for the signature to make things easier:
-
 ```gts
 // app/templates/my-route.gts
 import RoutableComponentRoute from "ember-routable-component";
@@ -202,8 +137,7 @@ export default class ModelWorksRoute extends Route<MyController>(
 }
 ```
 
-For Class-based components you can use the RoutableComponent 
-don't have this issue as they already accept a signature generic:
+For Class-based components you can use the RoutableComponent:
 
 ```gts
 // app/templates/my-route.gts