Remove inaccurate section about type alias names

Likely true at one point, but right now aliases actually do create a name that is used for Intellisense and errors. However, if you make aliases of another alias it just uses the first alias name; this has been marked as a bug, but it's possibly intended behavior: microsoft/TypeScript#19198

pages/Advanced Types.md

@@ -447,22 +447,7 @@ type Yikes = Array<Yikes>; // error
 
 ## Interfaces vs. Type Aliases
 
-As we mentioned, type aliases can act sort of like interfaces; however, there are some subtle differences.
-
-One difference is that interfaces create a new name that is used everywhere.
-Type aliases don't create a new name &mdash; for instance, error messages won't use the alias name.
-In the code below, hovering over `interfaced` in an editor will show that it returns an `Interface`, but will show that `aliased` returns object literal type.
-
-```ts
-type Alias = { num: number }
-interface Interface {
-    num: number;
-}
-declare function aliased(arg: Alias): Alias;
-declare function interfaced(arg: Interface): Interface;
-```
-
-A second more important difference is that type aliases cannot be extended or implemented from (nor can they extend/implement other types).
+The most important difference is that type aliases cannot be extended or implemented from (nor can they extend/implement other types).
 Because [an ideal property of software is being open to extension](https://en.wikipedia.org/wiki/Open/closed_principle), you should always use an interface over a type alias if possible.
 
 On the other hand, if you can't express some shape with an interface and you need to use a union or tuple type, type aliases are usually the way to go.