fix: typos

templates/charms-architecture.html

@@ -80,7 +80,7 @@ <h1 class="p-heading--2">What is a charm?</h1>
         <p class="p-heading--5">What is pebble</p>
       </div>
       <div class="col-6 col-start-large-7">
-        <p><a href="https://github.com/canonical/pebble">Pebble</a> is a lightweight, API-driven process supervisor. In Kuberenetes charms it is used to give workload containers something akin to an init system that will allow the charm container to interact with them.</p>
+        <p><a href="https://github.com/canonical/pebble">Pebble</a> is a lightweight, API-driven process supervisor. In Kubernetes charms it is used to give workload containers something akin to an init system that will allow the charm container to interact with them.</p>
         <p>Pebble allows to start, stop, restart and update services while taking into account service dependencies. Pebble implements custom "health checks" that can be configured to restart services when they fail, as well as the ability to forward logs to a remote Loki server.</p>
         <p>Pebble also includes a subsystem called notices, which allows the user to introspect various events that occur in the Pebble server, as well as record custom client events. The server saves notices to disk, so they persist across restarts, and expire after a notice-defined interval.</p>
       </div>
@@ -142,6 +142,7 @@ <h1 class="p-heading--2">How do charms work?</h1>
           <li class="p-list__item has-bullet">Leadership status</li>
         </ul>
         <p>Charms at runtime can read/write some data from the controller database and thereby access some configuration parameters to decide which code path to execute and how to manage its workload.</p>
+        <p>For more detailed information you can <a href="https://juju.is/docs/sdk/charm-lifecycle">read our charm lifecycle documentation article</a></p>
       </div>
     </div>
   </section>

templates/juju-architecture.html

@@ -100,7 +100,7 @@ <h1 class="p-heading--2">Juju high-level architecture</h1>
         <p>Interaction between applications is handled by integrations.</p>
       </div>
       <div class="row u-hide" id="integration">
-        <p>An <a href="https://juju.is/docs/juju/relation">integration</a> is a connection between applications.>
+        <p>An <a href="https://juju.is/docs/juju/relation">integration</a> is a connection between applications.
         <p>An integration between two applications is formed by connecting their endpoints. Endpoints can only be connected if they support the same interface and are of a compatible role (for example: requires to provides; provides to requires; peers to peers).</p>
         <p>Integrations mediate the configuration exchange between applications. Once an integration has been formed the two applications communicate directly (and not through the controller).</p>
       </div>

templates/why-juju.html

@@ -11,7 +11,7 @@
 <section class="p-section">
   <div class="row--50-50">
     <div class="col">
-      <h1 class="p-heading--2">Shift from configuration management to distributed system management</h1>
+      <h1 class="p-heading--2">Shift from application management to distributed system management</h1>
       {{ image(
           url="https://assets.ubuntu.com/v1/7e656757-Shift%20from%20application%20management.svg",
           alt="",
@@ -174,7 +174,7 @@ <h1 class="p-heading--2">What makes juju and charms different?</h1>
   <div class="u-fixed-width"><hr class="p-rule"></div>
   <div class="row--50-50">
     <div class="col">
-      <h1 class="p-heading--2">How does Juju compare to similar tools</h1>
+      <h1 class="p-heading--2">Juju compared to similar tools</h1>
     </div>
     <div class="col">
       <p class="p-heading--5">Juju’s focus is on system lifecycle management</p>