anchor.diff:  
   [id="snippet-file-metadata"]
   == Text snippet file metadata
  -Every text snippet should be placed in the snippets folder and should contain the following metadata at the top:
  +Every text snippet should be placed in the `snippets/` folder and should contain the following metadata at the top:
   
   ----
   // Text snippet included in the following assemblies: <1>
  
positive.code: ----
  <1> List of assemblies in which this text snippet is included.
  <2> List of modules in which this text snippet is included.
  <1> The content type for the file. For snippets, always use `:_content-type: SNIPPET`. Place this attribute before the anchor ID, the conditional that contains the anchor ID, or the first line of body text.
  
  [NOTE]
  ====
  
negative.code: 
  == Indicating Technology Preview features
  
  To indicate that a feature is in Technology Preview, include the `snippets/technology-preview.adoc` file in the feature's assembly or module to keep the supportability wording consistent across Technology Preview features. Provide a value for the `:FeatureName:` variable before you include this module.
  
  [source,text]
  ----
  :FeatureName: The XYZ plug-in
  \include::snippets/technology-preview.adoc[]
  ----
  
  == Indicating deprecated features
  
  To indicate that a feature is deprecated, include the `modules/deprecated-feature.adoc` file in the feature's assembly, or to each relevant assembly such as for a deprecated Operator, to keep the supportability wording consistent across deprecated features. Provide a value for the `:FeatureName:` variable before you include this module.
  
  See link:https://github.com/openshift/openshift-docs/pull/31776/files[an example] of how this is applied.
  
  