anchor.diff:  
   $$*software package*$$
   
  -a|*HTTPD* 
  +a|*HTTPD*
   
   *NetworkManager*
   
  
positive.code: |Try to be as descriptive as possible with the topic title or section headings without making them unnecessarily too long. Most importantly, we use title case in all topic titles and section headings. See http://titlecase.com/ for more information.
  |===
  
  
  
  == Links, hyperlinks, and cross references
  Links can be used to cross-reference internal topics, or send customers to external information resources for further reading. 
  
  === Internal Cross-References
  Whenever possible the link to another topic should be part of the actual sentence. Avoid creating links as a separate sentence that begins with "See [this topic] for more information on x". 
  
  [NOTE]
  ====
  Use the relative file path (from the file you are editing, to the file you are linking to), even if you are linking to the same directory that you are writing in. This makes search and replace operations to fix broken links much easier. 
  
  For example, if you are writing in *_architecture/core_concepts/deployments.adoc_* and you want to link to *_architecture/core_concepts/routes.adoc_* then you would need to include the path back to the first level of the topic directory: 
  
  ----
  link:../../architecture/core_concepts/routes.adoc
  
negative.code: 
  toc::[]
  
  == Topic metadata
  Every topic file should contain the following metadata at the top, with no line spacing in between, except where noted:
  
  ----
  