minor copyedits and update to interactive editor content

pages/_layouts/main.njk

@@ -120,7 +120,7 @@
   <section class="tools">
     <h2 id="tools">{{ content.tools.title }}</h2>
     {% if content.tools.subtitle %}
-      <h3>{{ content.tools.subtitle }}</h3>
+      <h3>{{ content.tools.subtitle | safe }}</h3>
     {% endif %}
     <div class="content">
       <div class="cards">

pages/index.adoc

@@ -12,7 +12,7 @@ It's packed with semantic elements and equipped with features to modularize and
 AsciiDoc content can be composed using a text editor, managed in a version control system, and published to multiple output formats.
 
 xref:#try[Get started,role=button]
-https://docs.asciidoctor.org/asciidoc/latest/syntax-quick-reference/[Quick Reference,button,role="button invert"]
+https://docs.asciidoctor.org/asciidoc/latest/syntax-quick-reference/[Quick Reference^,role=button invert]
 
 image::./assets/img/intellij-asciidoc-editor.png[]
 
@@ -29,12 +29,13 @@ image::./assets/img/intellij-asciidoc-editor.png[]
 //* image:./assets/img/fauna-logo-white.svg[]
 //* image:./assets/img/fedora-logo-white.svg[]
 
-[#about,separator=.]
-== One language, many output formats. Publish READMEs, books, and everything in between
+[#about]
+== One language, multiple outputs: Publish READMEs, books, and everything in between
 
 AsciiDoc provides all the semantic elements you need to write and publish technical books.
-You'll also find that AsciiDoc is an ideal fit for documentation.
+You'll also find AsciiDoc to be an ideal fit for documentation.
 And yet, it's simple enough to use for READMEs or taking notes.
+Explore the possibilities in the prepared screenshots.
 
 [.tab]
 --
@@ -85,15 +86,13 @@ image::./assets/img/man-page-git-for-each-ref.png[]
 --
 
 [#try-it-out.try]
-== Try AsciiDoc now: Experience the magic of a lightweight markup language
+== Try AsciiDoc now!: Experience the magic of a lightweight markup language
 
 You write AsciiDoc using plain text.
 That means most of what you type is what you want to communicate.
-You only enter markup characters when you need to encode meaning that can't be inferred.
-[.attn]#Try writing with AsciiDoc in the editor below to see for yourself!#
-// The next two lines should be used as hints in the content already in the interactive editor
-//Start a line with a series of equal signs to make a section title.
-//Prefix text with an asterisk to make an item in a list.
+You only need to add markup characters when you want to encode meaning that can't be inferred.
+For example, a section title starts with a series of equals signs and an unordered list item begins with one or more asterisks.
+[.attn]#Try writing AsciiDoc in the editor below to see for yourself!#
 
 [#editor-code,asciidoc]
 ------
@@ -116,11 +115,11 @@ puts 'Hello, World!'
 [#compare.compare]
 == How AsciiDoc stacks up: Compare AsciiDoc to other markup languages
 
-AsciiDoc is designed to strike a balance between systematic, machine-oriented syntax and plain text with minimalist markup.
-In fact, AsciiDoc can capture and encode nearly all of the semantics of a structured language while still being readable in source form.
+AsciiDoc is designed to strike a balance between systematic, machine-oriented syntax and plain text with minimal markup.
+This design affords AsciiDoc the ability to capture and encode nearly all the semantics of a structured language while still being readable in source form.
 
 Want to see how AsciiDoc stacks up against alternatives?
-Browse the sample documents below to compare.
+Browse the sample documents in this section to compare.
 
 [.tab.compare]
 --
@@ -282,21 +281,21 @@ AsciiDoc processors bundle a **stylesheet** that requires **no web development**
 [#specifications]
 == Specification process: Governed by a language specification, always evolving
 
-The AsciiDoc Language specification will ensure AsciiDoc is processed consistently by implementations that span language runtimes, authoring environments, and application integrations.
+The AsciiDoc Language specification was established to ensure that AsciiDoc continues to evolve and that it's processed consistently by implementations across language runtimes, authoring environments, and application integrations.
 The specification is managed and governed by the AsciiDoc Language project and, at a higher level, by the AsciiDoc Working Group at the Eclipse Foundation.
 Development of the specification is currently underway.
 
 https://asciidoc-wg.eclipse.org[Get involved,role=action]
 
 [#tools]
-== A growing ecosystem: Support for AsciiDoc
+== A growing ecosystem: AsciiDoc Tools & Support
 
 [.card]
 --
 [discrete]
 === Author
 
-Write and preview AsciiDoc content in your favorite text editor, IDE, or browser.
+Write, preview, and validate AsciiDoc content in your favorite text editor, IDE, or browser.
 
 https://docs.asciidoctor.org[Explore,role=action]
 --
@@ -306,7 +305,7 @@ https://docs.asciidoctor.org[Explore,role=action]
 [discrete]
 === Convert
 
-Convert your AsciiDoc documents to HTML, DocBook, PDF, and more with an AsciiDoc processor.
+Convert your AsciiDoc documents to HTML, DocBook, PDF, and more using an AsciiDoc processor.
 
 https://docs.asciidoctor.org[Explore,role=action]
 --
@@ -316,12 +315,12 @@ https://docs.asciidoctor.org[Explore,role=action]
 [discrete]
 === Publish
 
-Publish your content using static site generators and build tools that know how to process AsciiDoc.
+Publish your content using static site generators and build tools that know how to work with AsciiDoc.
 
 https://docs.asciidoctor.org[Explore,role=action]
 --
 
-https://docs.asciidoctor.org[Explore more Awesome AsciiDoc,role="explore action"]
+https://docs.asciidoctor.org[Explore more Awesome AsciiDoc,role=explore action]
 
 [#docs]
 == Get started with AsciiDoc today