Fix description of v1/v2 add-ons

The previous suggested change was supposed to include this, but missed
it because of nested code blocks inside the suggested change. Whoops!

README.md

@@ -9,17 +9,34 @@ With every release, we output the `--typescript` output of new ember apps to thi
 
 ## How to use TypeScript without `ember-cli-typescript`?
 
-
 Apps and v1 addons need to configure Babel to compile TypeScript files via the `ember-cli-babel` config, as described in the [ember-cli-babel](https://github.com/emberjs/ember-cli-babel#enabling-typescript-transpilation).
 
-Additionally, you will need the `tsconfig.json` generated by the Ember TypeScript blueprint (see above), and then can run [`glint`](https://typed-ember.gitbook.io/glint) or `tsc` directly on the CLI. (Again, see the official docs for details!)
+Additionally, you will need the `tsconfig.json` generated by the Ember TypeScript blueprint (see below for details), and then can run [`glint`](https://typed-ember.gitbook.io/glint) or `tsc` directly on the CLI. (Again, see the official docs for details!)
 
 ### Apps
 
 ```js
 'ember-cli-babel': {
   enableTypeScriptTransform: true,
 },
+```
+
+### v1 addons
+
+Configure this in the addon's `index.js` in the root of the project:
+
+```js
+module.exports = {
+  name: require('package').name,
+  options: {
+    'ember-cli-babel': {
+      enableTypeScriptTransform: true
+    }
+  }
+}
+```
+
+### v2 addons
 
 The [V2 Addon Blueprint](https://github.com/embroider-build/addon-blueprint) does not use nor need ember-cli-typescript, nor any of its features.