Fixed broken links in GH pages docs (#1736)

Author: sean-jeffrey

docs/.index

@@ -1,4 +1,3 @@
-title: Page Title
 collapse: true
 arrange:
     - index.md
@@ -11,4 +10,4 @@ arrange:
     - how-tos
     - faq.md
     - troubleshootings
-theme: readthedocs
+theme: readthedocs

docs/developers/build.md

@@ -47,7 +47,7 @@ The file will contain a JSON blob with the following shape:
 
 ### Deploy Application Gateway and AKS
 
-To deploy a fresh setup, please follow the steps for template deployment in the [greenfield](../setup/install-new.md) documentation.
+To deploy a fresh setup, please follow the steps for template deployment in the [greenfield](../setup/install.md) documentation.
 
 ### Using startup script
 

docs/developers/design.md

@@ -31,7 +31,7 @@ Let's take a look at each component:
 When any change is applied on the k8s cluster by the user, AGIC needs to listen to these changes in order to update the corresponding configuration on the Application Gateway.
 We use the kubernetes informers for this purpose which is a standard for watching resources on the K8S API server.
 
-When AGIC starts, it [sets up informers](../pkg/k8scontext/context.go) for watching following resources:
+When AGIC starts, it [sets up informers](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/pkg/k8scontext/context.go) for watching following resources:
 
 1. [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/): This is the top-level resource that AGIC monitors. It provides information about the layer-7 routing rules that need to be configured on the App Gateway.
 1. [Service](https://kubernetes.io/docs/concepts/services-networking/service/): Service provides an abstraction over the pods to expose as a network service. AGIC uses the service as logical grouping of pods to extract the IP addresses through the endpoints object created automatically along with the Service.
@@ -44,9 +44,9 @@ When starting the informers, AGIC also provides event handlers for each for crea
 
 ### 2. Worker
 
-[Worker](../../pkg/worker.go) is responsible for processing the events and performing updates.
+[Worker](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/pkg/worker/) is responsible for processing the events and performing updates.
 
-When Worker's `Run` function is called, it starts as a separate thread and waits on the `Work` channel. When an informers add an event to the channel, worker dequeues the event and checks whether the event is noise or is relevant. Events that are coming from unwatched namespaces and unreferenced pods/endpoints are skipped to reduce the churn. If the the last worker loop was run less than 1 second ago, it sleeps for the remainder and wakes up to space out the updates.  
+When Worker's `Run` function is called, it starts as a separate thread and waits on the `Work` channel. When an informers add an event to the channel, worker dequeues the event and checks whether the event is noise or is relevant. Events that are coming from unwatched namespaces and unreferenced pods/endpoints are skipped to reduce the churn. If the the last worker loop was run less than 1 second ago, it sleeps for the remainder and wakes up to space out the updates.
 After this, worker starts draining the rest of the events and calling the `ProcessEvent` function to process the event.
 
 `ProcessEvent` function does the following:
@@ -57,7 +57,7 @@ After this, worker starts draining the rest of the events and calling the `Proce
 
 ### 3. Application Gateway Config Builder
 
-This [component](../../pkg/appgw/configbuilder.go) is responsible for using the information in the local kubernetes cache and generating the corresponding Application Gateway configuration as an output.
+This [component](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/pkg/appgw/configbuilder.go) is responsible for using the information in the local kubernetes cache and generating the corresponding Application Gateway configuration as an output.
 
 Worker invokes the `Build` on this component which then generates various gateways sub-resources starting from leaf sub-resources like `probes`, `http settings` up to the `request routing rules`.
 

docs/features/appgw-ssl-certificate.md

@@ -9,7 +9,7 @@ This documents assumes you already have the following Azure tools and resources
 - [AAD Pod Identity](https://github.com/Azure/aad-pod-identity) installed on your AKS cluster
 - [Cloud Shell](https://shell.azure.com/) is the Azure shell environment, which has `az` CLI, `kubectl`, and `helm` installed. These tools are required for the commands below.
 
-Please use [Greenfield Deployment](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/setup/install-new.md) to install nonexistents.
+Please use [Greenfield Deployment](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/master/docs/setup/install.md) to install nonexistents.
 
 To use the new feature, make sure the AGIC version is at least at 1.2.0-rc3
 

docs/features/custom-ingress-class.md

@@ -37,7 +37,3 @@ To use a custom ingress class,
                 port:
                   number: 80
     ```
-
-## Reference
-
-* [Proposal Document](../../proposals\multiple-gateways-single-cluster.md)

docs/setup/install.md

@@ -22,8 +22,6 @@ You need to complete the following tasks prior to deploying AGIC on your cluster
 
 2. Set an AKS cluster for your workload.
 
-    > AKS cluster should have the workload identity feature enabled. [Learn how](../../aks/workload-identity-deploy-cluster.md#update-an-existing-aks-cluster) to enable workload identity on an existing AKS cluster.
-
     If using an existing cluster, ensure you enable Workload Identity support on your AKS cluster.  Workload identities can be enabled via the following:
 
     ```bash
@@ -119,7 +117,7 @@ If using an existing Application Gateway, make sure the following:
       --http-settings-protocol Http \
       --public-ip-address appgw-ip \
       --priority 10
-    
+
     APPGW_ID=$(az network application-gateway show --name $APPGW_NAME --resource-group $RESOURCE_GROUP --query "id" --output tsv)
     ```
 
@@ -183,7 +181,7 @@ AGIC can be installed by running the following commands:
     --set armAuth.identityClientID=$IDENTITY_CLIENT_ID \
     --set rbac.enabled=true \
     --version 1.7.3
-  
+
   # on aks cluster with windows node pools
   helm install ingress-azure \
     oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure \
@@ -210,7 +208,7 @@ AGIC can be upgraded by running the following commands:
     --set armAuth.identityClientID=$IDENTITY_CLIENT_ID \
     --set rbac.enabled=true \
     --version 1.7.3
-  
+
   # on aks cluster with windows node pools
   helm upgrade ingress-azure \
     oci://mcr.microsoft.com/azure-application-gateway/charts/ingress-azure \
@@ -242,9 +240,9 @@ via [Azure Cloud Shell](https://shell.azure.com/):
       ports:
       - containerPort: 8080
         protocol: TCP
-  
+
   ---
-  
+
   apiVersion: v1
   kind: Service
   metadata:
@@ -256,9 +254,9 @@ via [Azure Cloud Shell](https://shell.azure.com/):
     - protocol: TCP
       port: 80
       targetPort: 8080
-  
+
   ---
-  
+
   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata: