Architecture should be on top of the docs page

Signed-off-by: Anjali Telang <atelang@vmware.com>

site/content/docs/_index.md

@@ -13,6 +13,10 @@ As a Kubernetes cluster administrator or user, you can learn how Pinniped works,
 
 Have a question, comment, or idea? Please reach out via [GitHub Discussions](https://github.com/vmware-tanzu/pinniped/discussions) or [join the Pinniped community meetings]({{< ref "/community" >}}).
 
+## Background
+
+{{< docsmenu "background" >}}
+
 ## Tutorials
 
 {{< docsmenu "tutorials" >}}
@@ -24,7 +28,3 @@ Have a question, comment, or idea? Please reach out via [GitHub Discussions](htt
 ## Reference
 
 {{< docsmenu "reference" >}}
-
-## Background
-
-{{< docsmenu "background" >}}

site/content/docs/background/_index.md

@@ -6,7 +6,7 @@ menu:
   docs:
     name: Background
     identifier: background
-    weight: 110
+    weight: 11
 ---
 
 {{< docsmenu "background" >}}

site/content/docs/background/architecture.md

@@ -7,7 +7,7 @@ cascade:
 menu:
   docs:
     name: Architecture
-    weight: 100
+    weight: 20
     parent: background
 ---
 The principal purpose of Pinniped is to allow users to access Kubernetes
@@ -100,7 +100,7 @@ issue short-lived cluster certificates. (In the future, when the Kubernetes CSR
 provides a way to issue short-lived certificates, then the Pinniped credential exchange API
 will use that instead of using the cluster's signing keypair.)
 * Impersonation Proxy: Pinniped hosts an [impersonation](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#user-impersonation)
-proxy that sends requests to the Kubernetes API server with user information and permissions based on a token. 
+proxy that sends requests to the Kubernetes API server with user information and permissions based on a token.
 
 ## kubectl Integration