anchor.diff:  
   == Platform Requirements
   
  -The development toolchain / package group from the respective OS distribution
  -is required to build this package. In addition, a number of stable, well
  -maintained components are leveraged, rather than building and installing
  +The development toolchain package group from the respective OS distribution
  +is required to build this package. In addition, a number of stable, well-maintained
  +components are leveraged, rather than building and installing
   potentially conflicting versions.
   
  -On all platforms, in order to run Makefile.test there is a list of CPAN
  -dependencies required to invoke the perl-based Apache::Test framework.
  -These can be found under src/httpdtest-trunk/README after first running
  -the Makefile.gather phase. An immediate goal of this toolchain is to
  +On all platforms, in order to run `Makefile.test` there is a list of CPAN
  +dependencies required to invoke the perl-based `Apache::Test` framework.
  +These can be found under `src/httpdtest-trunk/README` after first running
  +the `Makefile.gather` phase. An immediate goal of this toolchain is to
   automate the local provisioning of those dependencies if not installed.
   
   === RedHat or Fedora Linux development package dependencies:
   
   For all steps the complete group of development tools is recommended, e.g.;
   
  - yum groupinstall 'C Development Tools and Libraries'
  + $ yum groupinstall 'C Development Tools and Libraries'
   
   or simply;
   
  - yum groupinstall 'Development Tools'
  + $ yum groupinstall 'Development Tools'
   
   Additional required tools which may not be included by default;
   
  - yum install cmake imake
  -
  -For the actual Makefile.build phase, a number of system component -devel
  + $ yum install cmake imake
  +
  +For the actual `Makefile.build` phase, a number of system component -devel
   packages are needed.
   
  - yum install libuuid-devel expat-devel libxml2-devel lua-devel pcre-devel zlib-devel
  + $ yum install libuuid-devel expat-devel libxml2-devel lua-devel pcre-devel zlib-devel
   
   These base packages are required for deployment (and are incidently installed
   with the -devel packages above; most are already present by default);
   
  - yum install libuuid expat libxml2 lua pcre zlib 
  -
  -* Note that following RHEL 7 / Fedora 21, yum becomes the dnf utility.
  + $ yum install libuuid expat libxml2 lua pcre zlib 
  +
  +* Note that following RHEL 7 / Fedora 21, `yum` becomes the `dnf` utility.
   The package names have remained the same.
   
   === Ubuntu or Debian development package dependencies:
   
  - apt-get install build-essential subversion xutils-dev cmake libtool
  - apt-get install libexpat1-dev libxml2-dev zlib1g-dev liblua5.2-0 libpcre3-dev
  + $ apt-get -y install \
  +     build-essential \
  +     cmake \
  +     git \
  +     subversion \
  +     xutils-dev\
  +     libexpat1-dev \
  +     liblua5.2-0 \
  +     libtool \
  +     libpcre3-dev \
  +     libxml2-dev \
  +     zlib1g-dev \
  +     wget
   
   == Phase 1: Gather Sources
   
    $ cd src/
  - $ make -f Makefile.gather [BLD={type}]
  + $ make -f ../mak/Makefile.gather [BLD={type}]
   
   BLD defines the build type: release - candidate - snapshot - bleed
   (case sensitive) where release is the default.
  
positive.code: == Phase 5: Package Installation Binaries
  
   $ cd dst/
   $ make -f Makefile.package [BLD={type}] [TAG={-suffix}]
  
  Copy the intermediate/temporary installation httpd server and dependent
  binaries into the dst/webserver/ tree to rewrite configurations files and
  scripts with as relocatable paths, add the instance management scripts,
  split the debugging symbols from the binaries, and tar up the package.
  
  This makefile must be run from the dst (not source or build) subdirectory.
   
  
  
negative.code: which are reasonably stable and up to date. On Windows,
  every component must be built from source.
  
  The build target is `/opt/pivotal/webserver/httpd-2.4/`
  on Linux and Windows, but is relocatable. Each has a
  long pathname, e.g. `httpd-2.4.25-$bldno/` which is
  symlinked from the 'expected' path. Non-release builds
  have additional pathname components such as `-snapshot`,
  `-bleed`, etc, and may have a TAG to distinguish two
  otherwise apparently identical builds.
  
  Build `\{pkg}` reflects the particular component, either
  the offical designation (`httpd-2.4.25/`), an indication
  of interim packages (`httpd-2.4.26-rc1/`), or the exact
  province of the file (`httpd-2.4.26-dev-r1872199/`)
  
  Several `\{bld}` schemas are expected; 'release' for the
  official packages, 'candidate' for packages anticipated
  for release, 'snapshot' for the working trees of the
  component's current maintenance trees, and 'bleed' for
  