anchor.diff:  In the Atom editor, you can use `Ctrl`+`J` to undo hard wrapping on a paragraph.
   ====
   
  +[id="assembly-file-metadata"]
   == Assembly file metadata
   Every assembly file should contain the following metadata at the top, with no line spacing in between, except where noted:
   
   ----
  -[id="<unique-heading-for-assembly>"]                            <1>
  -= Assembly title                                                <2>
  -include::modules/common-attributes.adoc[]                       <3>
  -:context: <unique-context-for-assembly>                         <4>
  -                                                                <5>
  -toc::[]                                                         <6>
  -----
  -
  -<1> A unique (within OpenShift docs) anchor id for this assembly. Use lowercase. Example: cli-developer-commands
  -<2> Human readable title (notice the '=' top-level header)
  -<3> Includes attributes common to OpenShift docs.
  +:_content-type: ASSEMBLY                                        <1>
  +[id="<unique-heading-for-assembly>"]                            <2>
  += Assembly title                                                <3>
  +include::modules/common-attributes.adoc[]                       <4>
  +:context: <unique-context-for-assembly>                         <5>
  +                                                                <6>
  +toc::[]                                                         <7>
  +----
  +
  +<1> The content type for the file. For assemblies, always use `:_content-type: ASSEMBLY`. Place this attribute before the anchor ID or, if present, the conditional that contains the anchor ID.
  +<2> A unique (within OpenShift docs) anchor ID for this assembly. Use lowercase. Example: cli-developer-commands
  +<3> Human readable title (notice the '=' top-level header)
  +<4> Includes attributes common to OpenShift docs.
   +
   [NOTE]
   ====
   The `{product-name}` and `{product-version}` common attributes are not defined in the `modules/common-attributes.adoc` file. Those attributes are pulled by AsciiBinder from the distro mapping definitions in the https://github.com/openshift/openshift-docs/blob/main/_distro_map.yml[_distro_map.yml] file. See xref:product-name-and-version[Product name and version] for more information on this topic.
   ====
   +
  -<4> Context used for identifying headers in modules that is the same as the anchor id. Example: cli-developer-commands.
  -<5> A blank line. You *must* have a blank line here before the toc.
  -<6> The table of contents for the current assembly.
  +<5> Context used for identifying headers in modules that is the same as the anchor ID. Example: cli-developer-commands.
  +<6> A blank line. You *must* have a blank line here before the toc.
  +<7> The table of contents for the current assembly.
   
   After the heading block and a single whitespace line, you can include any content for this assembly.
   
  
positive.code: //
  // * list of assemblies where this module is included              <1>
  
  [id="<module-anchor>_{context}"]                                   <2>
  = Module title                                                     <3>
  ----
  
  <1> List of assemblies in which this module is included.
  <2> A module anchor with {context} that must be lowercase and must match the module's file name.
  <3> Human readable title. To ensure consistency in the results of the
  leveloffset values in include statements, you must use a level one heading
  ( = ) for the module title.
  
  
negative.code: ----
  $ ln -s ../../images/ images
  $ ln -s ../../modules/ modules
  $ ln -s ../../snippets/ snippets
  ----
  +
  Be sure to adjust the number of levels to back up (`../`) depending on how deep your directory is.
  