fix: Get rid of duplicated Overview sections

Author: GildedRoach

src/content/docs/contributing/appstream.mdx

@@ -7,8 +7,6 @@ import { Aside } from "@astrojs/starlight/components";
 import { Code } from "astro:components";
 import RPMSpec from "@/components/spec.json";
 
-# Overview
-
 Terra supports AppStream MetaInfo, which enables your package to be picked up by graphical software 'store' applications, such as [KDE Plasma's Discover](https://apps.kde.org/discover) or [GNOME's Software app](https://apps.gnome.org/Software).
 This page will cover creating and installing AppStream MetaInfo to your package, but we also highly encourage you to read over the documentation [here](https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html).
 

src/content/docs/contributing/guidelines.mdx

@@ -7,8 +7,6 @@ import { Aside, Card, CardGrid } from "@astrojs/starlight/components";
 import { Code } from "astro:components";
 import RPMSpec from "@/components/spec.json";
 
-# Overview
-
 <Aside>
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
   NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and

src/content/docs/contributing/srpm.mdx

@@ -8,9 +8,7 @@ import { Code } from "astro:components";
 import { SearchTerra } from "@/components/mdx/searchterra";
 import RPMSpec from "@/components/spec.json";
 
-# Overview
-
-We provide custom Source RPM (SRPM) macros to ease packaging and better integrate our workflow. Please use these macros when possible in Terra.
+Terra provides custom Source RPM (SRPM) macros to ease packaging and better integrate our workflow. Please use these macros when possible in when contributing to Terra.
 
 These are provided in the `anda-srpm-macros` package. If you use them, make sure to add `anda-srpm-macros` as a <Code code={`BuildRequires:`} lang={RPMSpec} inline /> in the spec file.
 

src/content/docs/general/faq.mdx

@@ -3,8 +3,6 @@ title: FAQ
 description: "Frequently Asked Questions"
 ---
 
-# Repo Information
-
 How the Terra repo works, the reasons it exists, and other common questions.
 
 ## What packages does Terra have?

src/content/docs/general/infrastructure.mdx

@@ -3,8 +3,6 @@ title: Infrastructure
 description: The technical details behind the infrastructure and how different components work together.
 ---
 
-# How Terra Works
-
 This document outlines the process of how a package ends up to the end users.
 
 ## Terra Installation

src/content/docs/index.mdx

@@ -10,8 +10,6 @@ hero:
 
 import { Aside } from '@astrojs/starlight/components';
 
-# Overview
-
 Terra is a rolling repository RPM repository for Fedora Linux and its derivatives.
 With Terra, you can install the latest packages knowing that quality and security are assured.
 Terra is also a great way to distribute your software on Fedora and its derivatives.

src/content/docs/usage/installing.mdx

@@ -5,7 +5,7 @@ description: "Get access to the 1000+ packages that Fedora doesn't ship."
 
 import { Aside, Badge } from "@astrojs/starlight/components";
 
-# Adding Terra
+This page goes over how to install Terra for various distributions.
 
 ## Fedora and Derivatives
 

src/content/docs/usage/lifecycle.mdx

@@ -10,30 +10,30 @@ import { Aside } from "@astrojs/starlight/components";
   for these repos corresponds to the Fedora release version.
 </Aside>
 
-# Latest stable version of Fedora
+## Latest stable version of Fedora
 
 Full support. This branch is the main entrypoint for contributions and new packages. Packages are updated on a rolling release basis by Terra’s autoupdate system.
 
-# Non-latest, but supported versions of Fedora
+## Non-latest, but supported versions of Fedora
 
 We will provide updates for security issues, as tracked by Repology. Additionally we _may_ provide updates to resolve critical bugs. Besides those two cases, no new updates will be issued. No new packages may be directly submitted. It is also not guaranteed that the packages are up to date.
 
-# Branched Development Release
+## Branched Development Release
 
 <Aside type="caution">
   This branch may not exist if there is no current branched development release of Fedora.
 </Aside>
 
 When Fedora creates a new branched development release, we’ll branch off Terra’s stable repository to create a development/”preparatory” branch. This branch will automatically pull any additional contributions from stable and acts as a working ground to get Terra ready for the new release. When Fedora promotes this branched release to stable, we’ll do the same, setting this one as default. No guarantees are made for this branch during the development period.
 
-# Rawhide (Fedora’s rolling release)
+## Rawhide (Fedora’s rolling release)
 
 <Aside type="caution">
   You shouldn't be using this branch (or Rawhide in general) unless you know what you're doing.
 </Aside>
 
 Similarly to branched development releases, this branch will automatically pull contributions from the current stable branch. The purpose of this branch is to allow Rawhide users (usually enthusiast/developers) to have access to the vast Terra ecosystem, in addition to acting as a canary for any issues that might impact a future stable release. No guarantees are made for this branch.
 
-# EOL versions of Fedora
+## EOL versions of Fedora
 
 Completely unsupported. We will not provide any updates, even for critical security issues. While these repos might stay accessible on the internet, we reserve the right to purge them without notice.