fix xrefs to processor component (PR #2)

modules/attributes/pages/ref-document.adoc

@@ -880,7 +880,7 @@ Points to the _icons_ folder under `imagesdir` by default.
 |_empty_
 |{y}
 |{y}
-|xref:asciidoctor:backends:html/wrap.adoc[Wrap wide code listings].
+|xref:asciidoctor:html-backend:verbatim-line-wrap.adoc[Wrap wide code listings].
 
 |pygments-css
 |

modules/document/pages/doctypes.adoc

@@ -14,7 +14,7 @@ A book only has chapters and special sections, whereas a multi-part book is divi
 Man page (`manpage`)::
 Used for producing a roff or HTML-formatted manual page (man page) for Unix and Unix-like operating systems.
 This doctype instructs the parser to recognize a special document header and section naming conventions for organizing the AsciiDoc content as a man page.
-See xref:asciidoctor:backends:manpage/convert-to-man-page.adoc[] for details on how structure a man page using AsciiDoc and generate it with Asciidoctor.
+See xref:asciidoctor:manpage-backend:index.adoc[] for details on how structure a man page using AsciiDoc and generate it with Asciidoctor.
 
 Inline (`inline`)::
 Asciidoctor only.

modules/document/pages/header.adoc

@@ -66,7 +66,7 @@ Any attributes defined below the first blank line are not part of the document h
 
 The header is optional when the `doctype` is `article` or `book`.
 A header is required when the document type is `manpage`.
-See the xref:asciidoctor:backends:manpage/convert-to-man-page.adoc#man-page-doctype[man page doctype] section for manual page (man page) requirements.
+See the xref:asciidoctor:manpage-backend:index.adoc[manpage doctype] section for manual page (man page) requirements.
 
 == Header processing
 
@@ -78,4 +78,4 @@ If you don't want the header of a document to be displayed, set the `noheader` a
 
 Many static site generators, such as Jekyll and Middleman, rely on front matter added to the top of the document to determine how to convert the content.
 Asciidoctor has a number of attributes available to correctly handle front matter.
-See xref:asciidoctor:backends:html/front-matter.adoc[] to learn more.
+See xref:asciidoctor:html-backend:skip-front-matter.adoc[] to learn more.

modules/stem/pages/stem.adoc

@@ -5,7 +5,7 @@
 :url-latexmath: https://docs.mathjax.org/en/latest/input/tex/index.html
 :url-mathjax-docs: https://meta.math.stackexchange.com/questions/5020/mathjax-basic-tutorial-and-quick-reference
 
-If you need to display Science, Technology, Engineering and Math (STEM) expressions in your output, the HTML backend integrates with xref:asciidoctor:integrations:mathjax.adoc[MathJax] and Docbook backend integrates with the xref:asciidoctor:integrations:asciimath-gem.adoc[AsciiMath RubyGem].
+If you need to display Science, Technology, Engineering and Math (STEM) expressions in your output, the HTML backend integrates with xref:asciidoctor:stem:mathjax.adoc[MathJax] and Docbook backend integrates with the xref:asciidoctor:stem:asciimath-gem.adoc[AsciiMath RubyGem].
 
 == Activating STEM support
 

modules/verbatim/pages/source-highlighter.adoc

@@ -54,9 +54,9 @@ You can also declare this attribute using the CLI or API.
 |===
 
 To use Rouge, CodeRay, or Pygments, you must have the appropriate library installed on your system.
-See xref:asciidoctor:integrations:rouge.adoc[], xref:asciidoctor:integrations:coderay.adoc[], or xref:asciidoctor:integrations:pygments.adoc[] for installation instructions.
+See xref:asciidoctor:source-highlighters:rouge.adoc[], xref:asciidoctor:source-highlighters:coderay.adoc[], or xref:asciidoctor:source-highlighters:pygments.adoc[] for installation instructions.
 
-If you're using the client-side library xref:asciidoctor:integrations:highlightjs.adoc[], there's no need to install additional libraries.
+If you're using the client-side library xref:asciidoctor:source-highlighters:highlightjs.adoc[], there's no need to install additional libraries.
 The generated HTML will load the required source files from a CDN, custom URL, or file path.
 
 .Source Highlighter vs. Syntax Highlighter