anchor.diff:    while compiling the application:
   
     * `TRANSLATIONS` is a string containing the content of the translation file.
  -  * `TRANSLATIONS_FORMAT` is the format of the file: `xlf`, `xlif` or `xtb`.
  +  * `TRANSLATIONS_FORMAT` is the format of the file: `xlf`, `xlif`, or `xtb`.
     * `LOCALE_ID` is the locale of the target language.
   
  -  The `getTranslationProviders` function in the following `src/app/i18n-providers.ts` 
  +  The `getTranslationProviders()` function in the following `src/app/i18n-providers.ts`
     creates those providers based on the user's _locale_
     and the corresponding translation file:
   +makeExample('cb-i18n/ts/src/app/i18n-providers.ts', null, 'src/app/i18n-providers.ts')
  
positive.code: 
  .l-main-content
  :marked
    The entire template translation is complete. It's 
    time to incorporate that translation into the application.
  
  #app-pre-translation
  
negative.code: 
    To merge the translated text into component templates,
    compile the application with the completed translation file.
    The process is the same whether the file is in `.xlf` format or
    in another format that Angular understands, such as `.xlif` or `.xtb`.
  
    You provide the Angular compiler with three new pieces of information:
  
      * The translation file.
      * The translation file format.
      * The   <a href="https://en.wikipedia.org/wiki/XLIFF" target="_blank">_Locale ID_</a>
      (`es` or `en-US` for instance).
  
    _How_ you provide this information depends upon whether you compile with
    the JIT (_Just-in-Time_) compiler or the AOT (_Ahead-of-Time_) compiler.
  
      * With [JIT](#jit), you provide the information at bootstrap time.
      * With [AOT](#aot), you pass the information as `ngc` options.
  
  a#jit
  .l-main-section
  :marked
    ### Merge with the JIT compiler
  
    The JIT compiler compiles the application in the browser as the application loads.
    Translation with the JIT compiler is a dynamic process of:
  
  