changes type provider terminology to be in line with the upcoming talk

xeno-by · xeno-by · commit 2822c1d439bd · 2014-04-04T10:28:57.000+02:00
diff --git a/overviews/macros/typeproviders.md b/overviews/macros/typeproviders.md
@@ -15,13 +15,13 @@ languages: [ja]
 Type providers aren't implemented as a dedicated macro flavor, but can rather built on top of the functionality
 that Scala macros already provide.
 
-There are two strategies of emulating type providers: one based on structural types (referred to as "fake type providers")
-and one based on macro annotations (referred to as "real type providers"). The former builds on functionality available
+There are two strategies of emulating type providers: one based on structural types (referred to as "anonymous type providers")
+and one based on macro annotations (referred to as "public type providers"). The former builds on functionality available
 in 2.10.x and 2.11, while the latter requires macro paradise. Both strategies can be used to implement erased type providers
 as described below.
 
 Note that macro paradise is needed both to compile and to expand macro annotations,
-which means that both authors and users of real type providers will have to add macro paradise to their builds.
+which means that both authors and users of public type providers will have to add macro paradise to their builds.
 However, after macro annotations expand, the resulting code will no longer have any references to macro paradise
 and won't require its presence at compile-time or at runtime.
 
@@ -43,7 +43,7 @@ are local in the sense that the scope of their expansions is limited: [https://g
 1. Make generated definitions optionally erasable (Scala supports erasure for a number of language constructs,
 e.g. for abstract type members and value classes, but the mechanism is not extensible, which means that macro writers can't customize it).
 
-### Fake type providers
+### Anonymous type providers
 
 Even though the scope of definitions introduced by expansions of def macros is limited to those expansions,
 these definitions can escape their scopes by turning into structural types. For instance, consider the `h2db` macro that
@@ -84,9 +84,9 @@ it has performance problems caused by the fact that Scala emits reflective calls
 of structural types. There are several strategies of dealing with that, but this margin is too narrow to contain them
 so I refer you to an amazing blog series by Travis Brown for details: [post 1](http://meta.plasm.us/posts/2013/06/19/macro-supported-dsls-for-schema-bindings/), [post 2](http://meta.plasm.us/posts/2013/07/11/fake-type-providers-part-2/), [post 3](http://meta.plasm.us/posts/2013/07/12/vampire-methods-for-structural-types/).
 
-Please note that fake type providers must be [whitebox](/overviews/macros/blackbox-whitebox.html), otherwise they will not work.
+Please note that anonymous type providers must be [whitebox](/overviews/macros/blackbox-whitebox.html), otherwise they will not work.
 
-### Real type providers
+### Public type providers
 
 With the help of [macro paradise](/overviews/macros/paradise.html) and its [macro annotations](/overviews/macros/annotations.html), it becomes
 possible to easily generate publicly visible classes, without having to apply workarounds based on structural types. The annotation-based
@@ -107,7 +107,7 @@ and singleton types can provide an equivalent of erased type providers in F#. Co
 should be declared as usual, whereas classes that should be erased to a given upper bound should be declared as type aliases
 to that upper bound parameterized by a singleton type that carries unique identifiers. With that approach, every new generated type
 would still incur the overhead of additional bytecode to the metadata of type aliases, but that bytecode would be significantly smaller
-than bytecode of a full-fledged class. This technique applies to both fake and real type providers.
+than bytecode of a full-fledged class. This technique applies to both anonymous and public type providers.
 
     object Netflix {
       type Title = XmlEntity["http://.../Title".type]
