remove Glimmer and Typescript references

Author: jenweber

guides/release/components/defining-a-component.md

@@ -285,9 +285,7 @@ export default class BlogPost extends Component {}
 > You may notice that we're importing the component from `@glimmer` instead of
 > `@ember`. The Glimmer VM is the underlying rendering engine in Ember, and
 > Glimmer.js is a minimal component framework built on top of the Glimmer VM.
-> Ember and Glimmer.js use the same component class, which allows you to share
-> code between Ember and Glimmer.js apps. For more details on Glimmer.js, check
-> out [its documentation](https://glimmerjs.com/)
+> Althought components are imported from this outside library, you don't need worry about learning Glimmer separately from Ember.
 
 You can add methods and fields to the component, and then access them from the
 component's template. For instance, we could add the `sectionClass` property
@@ -371,22 +369,6 @@ Events](../actions-and-events).
 
 #### Component Hooks and Properties
 
-Components have the following class signature (this given as a TypeScript class
-signature for clarity and brevity, if you don't know TypeScript, don't worry!
-We'll explain what it all means in just a minute):
-
-```js
-class GlimmerComponent {
-  args: object;
-
-  isDestroying: boolean;
-  isDestroyed: boolean;
-
-  constructor(owner: unknown, args: object);
-  willDestroy();
-}
-```
-
 The component class has 3 properties:
 
 - `args`: The arguments that were passed to the component

guides/release/state-management/index.md

@@ -48,7 +48,7 @@ in a popup, the page you're on, or the color of a button, Ember needs to respond
 to that change!
 
 Ember's primary system for detecting changes to state is _tracked properties_.
-If you read the section on Glimmer components, you'll probably recognize these.
+If you read the section on components, you'll probably recognize these.
 They're properties that are decorated with the `@tracked` decorator:
 
 ```js