anchor.diff:  |======================
   
   You select a *profile* when running *SysTest* by passing `-P <profile name>` on
  -the command line. For more details, see the [[interfaces documentation|interfaces]].
  +the command line. For more details, see the 
  +[[Interfaces Documentation|interfaces]].
  
positive.code: *Settings* are the most basic form of configuration that *SysTest* handles, and
  are simply a means to externalise certain data you wish to make use of in your
  tests. There is no _special_ format for this data, nor are there any allowed 
  (or disallowed) _elements_. Settings can be extracted at runtime using the 
  [[Configuration API|systest_config]], or accessed in and used in 
  _string-expressions_ by referencing the `settings` group. For example:
  
  ```erlang
  {web_server_url, "${settings.base_url}/login.html"}.
  ```
  
  Settings are sourced from +./resources/default.settings+ initially, if it 
  exists. Then the _base directory_ is searched (recursively) for a file whose
  
negative.code: of the `USER` environment variable. These two files are then merged, with the
  _configuration elements_ from the latter file overwriting those from the 
  default.
  
  Settings can be extracted at runtime using the 
  [[Configuration API|systest_config]], or accessed in and used in 
  _string-expressions_ by referencing the `settings` group. For example:
  
  ```erlang
  {web_auth_url, "${settings.base_url}/login.html"}.
  ```
  
  == Resource Configuration Files
  
  These configuration files define the various *Resources* that can be made to
  participate in a test run. For more information about *Resources* in general,
  see the [[Concepts/Overview|concepts]] page.
  
  *Resources Configuration Files* are sources from +./resources/*.resource+ by
  default, though like most config locations, this can be overridden by the
  current *Profile* (more on this later).
  
  == Profiles
  
  