Fix rendering issues, make linter happy

Signed-off-by: Marcela Melara <marcela.melara@intel.com>

Author: marcelamelara

docs/_data/nav/v1.0.yml

@@ -6,6 +6,7 @@
 
 - title: Current activities
   url: /current-activities
+  description: Additions and updates actively being developed
 
 - title: Understanding SLSA
   description: >

docs/_data/nav/v1.1.yml

@@ -6,6 +6,7 @@
 
 - title: Current activities
   url: /current-activities
+  description: Additions and updates actively being developed
 
 - title: Understanding SLSA
   description: >

docs/community.md

@@ -78,12 +78,12 @@ developing tooling, we welcome your contributions.
 </div>
             </div>
             <div class="w-full md:w-1/2">
-			<div class="rounded-lg text-green p-5 border border-green-400 inline-block mb-8 h4">SLSA v1.0 is available now!</div>
+                <div class="rounded-lg text-green p-5 border border-green-400 inline-block mb-8 h4">SLSA v1.0 is available now!</div>
                 <p>
                 The community has been hard at work since the release of
-				<a href="spec/v1.0/">SLSA v1.0</a> in 2023 to expand the breadth
-				and depth of the specification with updates and new tracks.
-				For more information, see our <a href="/spec/current-activities">current activities</a> page!
+                <a href="spec/v1.0/">SLSA v1.0</a> in 2023 to expand the breadth
+                and depth of the specification with updates and new tracks.
+                For more information, see our <a href="/spec/current-activities">current activities</a> page!
                 <br><br>
 Google has been using an internal version of SLSA since 2013 and requires it for all of their production workloads.</p>
             </div>

docs/current-activities.md

@@ -5,14 +5,15 @@ tracks. This page provides a summary of current ongoing activities.
 layout: standard
 ---
 
+## Current Activities
+
 Since the release of <a href="spec/v1.0/">SLSA v1.0</a> in 2023,
 the SLSA community has been hard at work to expand the breadth
 and depth of the specification with updates and new tracks.
-Learn how you can [get involved](https://slsa.dev/community#get-involved)!
 
-<section id="source-track">
+Learn how you can [get involved](https://slsa.dev/community#get-involved)!
 
-## Source track
+### Source track
 
 A Source track will provide protection against tampering of the source code
 prior to the build.
@@ -21,11 +22,7 @@ The current [draft version (v1.1)](source-requirements.md) describes levels
 of increasing tamper resistance and ways consumers might verify properties
 of source revisions using SLSA source provenance attestations.
 
-</section>
-
-<section id="buildenv-track">
-
-## Build Environment track
+### Build Environment track
 
 The goal of a Build Environment track is to enable the detection of tampering
 with core components of the compute environment executing builds.
@@ -42,14 +39,9 @@ of the Build Environment track includes the following requirements:
 These requirements are **subject to significant change** while this track
 is in draft.
 
-</section>
-
-<section id="dependency-track">
-## Dependency track
+### Dependency track
 
 Building upon the foundation laid by S2C2F, the depedency track defines
 requirements for consuming dependencies.
 
 **TODO**: Expand this section
-
-</section>