Format the doc for gitrepositories to wrap at 80 chars

Signed-off-by: Dipti Pai <[email protected]>

docs/spec/v1/gitrepositories.md

@@ -214,26 +214,34 @@ this via the `--password` flag.
 
 ### Provider
 
-`.spec.provider` is an optional field that allows specifying an OIDC provider used for
-authentication purposes.
+`.spec.provider` is an optional field that allows specifying an OIDC provider
+used for authentication purposes.
 
 Supported options are:
 
 - `generic`
 - `azure`
 
-When provider is not specified, it defaults to `generic` indicating that mechanisms using `spec.secretRef` are used for authentication. 
+When provider is not specified, it defaults to `generic` indicating that
+mechanisms using `spec.secretRef` are used for authentication. 
 
 #### Azure
 
-The `azure` provider can be used to authenticate to Azure DevOps repositories automatically using Workload Identity. 
+The `azure` provider can be used to authenticate to Azure DevOps repositories
+automatically using Workload Identity. 
 
 ##### Pre-requisites
 
-- Ensure that your Azure DevOps Organization is [connected to Microsoft Entra](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/connect-organization-to-azure-ad?view=azure-devops) 
-- Ensure Workload Identity is properly set up on your cluster and the mutating webhook is installed.
-- Create a managed identity and federated identity between the source-controller service account and managed identity. Please take a look at this [guide](https://azure.github.io/azure-workload-identity/docs/quick-start.html#6-establish-federated-identity-credential-between-the-identity-and-the-service-account-issuer--subject)
-- Ensure that the managed identity has required permissions to access the Azure DevOps repository as described [here](https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/service-principal-managed-identity?view=azure-devops#2-add-and-manage-service-principals-in-an-azure-devops-organization)
+- Ensure that your Azure DevOps Organization is [connected to Microsoft
+  Entra](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/connect-organization-to-azure-ad?view=azure-devops) 
+- Ensure Workload Identity is properly set up on your cluster and the mutating
+  webhook is installed.
+- Create a managed identity and federated identity between the source-controller
+  service account and managed identity. Please take a look at this
+  [guide](https://azure.github.io/azure-workload-identity/docs/quick-start.html#6-establish-federated-identity-credential-between-the-identity-and-the-service-account-issuer--subject)
+- Ensure that the managed identity has required permissions to access the Azure
+  DevOps repository as described
+  [here](https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/service-principal-managed-identity?view=azure-devops#2-add-and-manage-service-principals-in-an-azure-devops-organization)
 
 Add the following patch in `flux-system/kustomization.yaml` file: