Update website

Author: acoburn

website/download.html

@@ -33,17 +33,26 @@ <h2>Downloads</h2>
 
       <h3>Trellis Implementations</h3>
 
-      <p>Known implementations of the Trellis persistence layer are included below.</p>
+      <p>
+        There are several Trellis-based applications. Each has different performance characteristics: for example,
+        the Triplestore-based server (Trellis Application) is very easy to deploy and is ideal for single-node installations. The
+        Kafka-based server (Rosid), on the other hand, is much easier to scale horizontally.
+      </p>
+
+      <section id="triplestore" typeof="doap:Project schema:SoftwareApplication">
+        <h4 property="doap:name schema:name">Trellis Application</h4>
+
+        <p property="doap:description">A Trellis implementation using an internal triplestore.</p>
+        <p><a property="doap:download-page" href="https://github.com/trellis-ldp/trellis/releases">Latest Release</a></p>
+        <p><a property="doap:repository" href="https://github.com/trellis-ldp/trellis">Source Code</a></p>
+      </section>
 
       <section id="rosid" typeof="doap:Project schema:SoftwareApplication">
         <h4 property="doap:name schema:name">Rosid</h4>
 
         <p property="doap:description">A Trellis implementation using a file-based persistence layer and an internal Kafka event bus.</p>
-
         <p><a property="doap:download-page" href="https://github.com/trellis-ldp/trellis-rosid/releases">Latest Release</a></p>
-
         <p><a property="doap:repository" href="https://github.com/trellis-ldp/trellis-rosid">Source Code</a></p>
-
         <p>Note: be sure to download both the <code>trellis-rosid-app</code> and the <code>trellis-processing</code> artifacts.</p>
       </section>
 

website/index.html

@@ -61,10 +61,9 @@ <h3>Scalability</h3>
         <h3>Durability</h3>
         <p>
           Data integrity is vitally important for content that is stored for years and decades. Trellis makes it possible to retrieve
-          the state of any resource at any, arbitrary point in time. This also means that nothing is ever truly deleted (though if you
-          need to purge a resource from the persistence layer, there is a mechanism for that). For every operation that changes a
-          resource, there is a full audit log available through standard LDP mechanisms. This audit log lists who made what change and
-          when that change was made.
+          the state of any resource at any, arbitrary point in time. This also means that nothing is ever truly deleted. For every
+          operation that changes a resource, there is a full audit log available through standard LDP mechanisms.
+          This audit log lists who made what change and when that change was made.
         </p>
       </section>
 
@@ -83,7 +82,7 @@ <h3>Flexibility</h3>
           Because Trellis is built on top of <a href="https://www.w3.org/TR/ldp-primer/">LDP</a>, clients that interact with it
           tend to use a lot of RDF (e.g. <a href="https://json-ld.org/">JSON-LD</a>). Trellis
           enforces only a very minimal set of restrictions on what RDF is allowable: basically, if LDP prohibits it, Trellis does not
-          allow it, but otherwise, pretty much anything goes. You can use any RDF vocabulary; you can store binaries of any type. Any
+          allow it; otherwise, pretty much anything goes. You can use any RDF vocabulary; you can store binaries of any type. Any
           special handling of particular content types needs to be handled in another layer of your software stack.
         </p>
       </section>