chore: Some cleanup of very old docs and duplicative pages

docs/admin/deploy/machine-images/aws-oneclick.mdx

@@ -48,8 +48,6 @@ Choose an AWS Region in the launcher below and click **Launch Stack**. When prom
 
 <AWSOneClickLaunchForm />
 
-If you're running into any problem, see our [Troubleshooting guide](/admin/troubleshooting).
-
 ### Confirm you can access Sourcegraph
 
 Find the URL of your Sourcegraph instance in the **Outputs** section of the AWS Stack. On first launch, Sourcegraph may take ~5 minutes to start and may display a `404 not found` page temporarily.

docs/admin/enterprise_getting_started_guide/index.mdx

@@ -5,6 +5,7 @@ If you're deploying a new Enterprise instance, this page covers our most frequen
 ## Admin articles
 
 ### General
+
 - [Deployment overview](/admin/deploy/)
 - [Resource estimator](/admin/deploy/resource_estimator)
 - [SAML config](/admin/auth/saml/)
@@ -21,12 +22,14 @@ If you're deploying a new Enterprise instance, this page covers our most frequen
 - [Changelog](https://sourcegraph.com/changelog) to track releases and updates
 
 ### Docker-compose
+
 - [Basic installation guide](/admin/deploy/docker-compose/)
 - [AWS installation](/admin/deploy/docker-compose/aws)
 - [Digital Ocean installation](/admin/deploy/docker-compose/digitalocean)
 - [Google Cloud installlation](/admin/deploy/docker-compose/google_cloud)
 
 ## User articles
+
 - [Search syntax](/code-search/queries)
 - [Search filters](/code-search/queries#filters-all-searches)
 - [Example batch changes](/batch-changes/examples)

docs/admin/executors/executors_config.mdx

@@ -63,4 +63,4 @@ The following environment variables are specific to the native Kubernetes Execut
 | `KUBERNETES_JOB_POD_ANNOTATIONS`                               | N/A               | The JSON encoded annotations to add to the Kubernetes Job Pods. e.g. `{"foo": "bar", "faz": "baz"}`                                                                                                    |
 | `KUBERNETES_IMAGE_PULL_SECRETS`                                | N/A               | The names of Kubernetes image pull secrets to use for pulling images. e.g. my-secret,my-other-secret                                                                                                   |
 
-<Callout type="note">Note: `EXECUTOR_KUBERNETES_NAMESPACE` should be set to either "default" or the specific namespace where your Executor is deployed.</Callout>
+<Callout type="note">`EXECUTOR_KUBERNETES_NAMESPACE` should be set to either "default" or the specific namespace where your Executor is deployed.</Callout>

docs/admin/executors/index.mdx

@@ -39,7 +39,7 @@ Deciding how to deploy the executor depends on your use case. For users that wis
 
 ## How it works
 
-Executor instances are capable of being deployed in a variety of ways. Each runtime varies in _how_ jobs are executed.
+Executor instances are capable of being deployed in a variety of ways. Each runtime varies in how jobs are executed.
 
 ### Locally with src-cli
 
@@ -133,11 +133,8 @@ Executor instances are capable of being deployed in a variety of ways. Each runt
 
 > NOTE: This is an experimental feature.
 
-
-
 <img src="https://storage.googleapis.com/sourcegraph-assets/executor_kubernetes_native_arch.png" alt="Executors architecture - native kubernetes" />
 
-
 1.  The executor image is started as a pod in a Kubernetes node
 2.  The executor pulls for available Jobs from a Sourcegraph API
 3.  A user initiates a process that creates executor Jobs.
@@ -152,10 +149,6 @@ Executor instances are capable of being deployed in a variety of ways. Each runt
 9.  Logs are streamed from the executor to a Sourcegraph API
 10.  The executor calls a Sourcegraph API to that "complete" the Job.
 
-### Native execution
-
-Read more in [Native execution](/admin/executors/native_execution).
-
 ### Docker-in-Docker Kubernetes
 
 > NOTE: This is an experimental feature.
@@ -180,4 +173,5 @@ Read more in [Native execution](/admin/executors/native_execution).
 10.  The executor calls a Sourcegraph API to that "complete" the Job.
 
 ## Troubleshooting
+
 Refer to the [Troubleshooting Executors](/admin/executors/executors_troubleshooting) document for common debugging operations.

docs/admin/faq.mdx

@@ -128,6 +128,21 @@ You can then access your dashboards directly through your Grafana instance URL.
 
 This error is expected if your instance was not [deployed with Kubernetes](/admin/deploy/kubernetes/). The Instrumentation page is currently only available for Kubernetes instances.
 
-## Troubleshooting
+## Sourcegraph is making unauthorized requests to the git server
 
-Please refer to our [dedicated troubleshooting page](/admin/troubleshooting).
+This is normal and happens whenever git is used over HTTP. To avoid unnecessarily sending a password over HTTP, git first
+makes a request without the password included. If a 401 Unauthorized is returned, git sends the request with the password.
+
+More information can be found [here](https://confluence.atlassian.com/bitbucketserverkb/two-401-responses-for-every-git-opperation-938854756.html).
+
+If this behaviour is undesired, the `gitURLType` in the [external service configuration](/admin/code_hosts/github#configuration)
+should be set to `ssh` instead of `http`. This will also require [ssh keys to be set up](/admin/repo/auth#repositories-that-need-http-s-or-ssh-authentication).
+
+## Sourcegraph is not returning results from a repository unless "repo:" is included
+
+If you can get repository results when you explicitly include `repo:{your repository}` in your search, but don't see any results from that repository when you don't, there are a few possible causes:
+
+- The repository is a fork repository (excluded from search results by default) and `fork:yes` is not specified in the search query.
+- The repository is an archived repository (excluded from search results by default) and `archived:yes` is not specified in the search query.
+- There is an issue indexing the repository: check the logs of worker and/or search-indexer.
+- The search index is unavailable for some reason: try the search query `repo:<the_repository> index:only`. If it returns no results, the repository has not been indexed.