Remove mentions of sg/sg repo (#1098)

Removes mentions of sg/sg repo.

Author: MaedahBatool

docs/admin/auth/index.mdx

@@ -56,8 +56,7 @@ order:
   use the [OpenID Connect provider](#openid-connect).
 - If you wish to use LDAP and cannot use the GitHub/GitLab OAuth provider as described above, or if
   you wish to use another authentication mechanism that is not yet supported, please [contact
-  us](https://github.com/sourcegraph/sourcegraph/issues/new?template=feature_request) (we respond
-  promptly).
+  us](https://sourcegraph.com/contact)
 
 Most users will use only one auth provider, but you can use multiple auth providers if desired to
 enable sign-in via multiple services. Identities from different providers will be mapped to a

docs/admin/auth/saml/index.mdx

@@ -81,7 +81,7 @@ Error prefetching SAML service provider metadata
 
 > NOTE: Email or NameID changes in the identity provider are not automatically reflected in Sourcegraph. Admins may manually update a users email via the admin interface at `https://example-sourcegraph.com/users/<user>/settings/emails`, or remove the user and recreate a new account.
 >
-> Work is planned to support SCIM on SAML auth providers, which should automate this process. ([tracking issue](https://github.com/sourcegraph/sourcegraph/issues/22732))
+> Work is planned to support SCIM on SAML auth providers, which should automate this process.
 
 ### How to control user sign-up and sign-in
 

docs/admin/beta_and_experimental_features.mdx

@@ -4,7 +4,7 @@ Sourcegraph often beta tests major features before we make them generally availa
 
 Exposing beta and experimental features gives you an opportunity to try our newest features sooner.
 
-In return, your feedback helps us make sure that our new features are reliable and useful, and we appreciate any and all feedback you want to provide. You can [file an issue](https://github.com/sourcegraph/sourcegraph/issues/new/choose), email it directly to [[email protected]](mailto:[email protected]), or use the in-app feedback modal.
+In return, your feedback helps us make sure that our new features are reliable and useful, and we appreciate any and all feedback you want to provide. You can email us directly to [[email protected]](mailto:[email protected]).
 
 ## Both beta and experimental features
 

docs/admin/code_hosts/github.mdx

@@ -241,7 +241,7 @@ There are four fields for configuring which repositories are mirrored/synchroniz
 
 - [`repos`](/admin/code_hosts/github#repos)A list of repositories in `owner/name` format. The order determines the order in which we sync repository metadata and is safe to change.
 - [`orgs`](/admin/code_hosts/github#orgs)A list of organizations (every repository belonging to the organization will be cloned).
-- [`repositoryQuery`](/admin/code_hosts/github#repositoryQuery)A list of strings with three pre-defined options (`public`, `affiliated`, `none`, none of which are subject to result limitations), and/or a [GitHub advanced search query](https://github.com/search/advanced). Note: There is an existing limitation that requires the latter, GitHub advanced search queries, to return [less than 1000 results](#repositoryquery-returns-first-1000-results-only). See [this issue](https://github.com/sourcegraph/sourcegraph/issues/2562) for ongoing work to address this limitation.
+- [`repositoryQuery`](/admin/code_hosts/github#repositoryQuery)A list of strings with three pre-defined options (`public`, `affiliated`, `none`, none of which are subject to result limitations), and/or a [GitHub advanced search query](https://github.com/search/advanced). Note: There is an existing limitation that requires the latter, GitHub advanced search queries, to return [less than 1000 results](#repositoryquery-returns-first-1000-results-only).
 - [`exclude`](/admin/code_hosts/github#exclude)A list of repositories to exclude which takes precedence over the `repos`, `orgs`, and `repositoryQuery` fields.
 
 ## Rate limits

docs/admin/config/advanced_config_file.mdx

@@ -119,7 +119,7 @@ When you upgrade Sourcegraph, you should do the following to ensure your configu
 
 It is essential to follow the above steps after **every** Sourcegraph version update, because we only guarantee migrations remain valid across two minor versions. If you fail to apply a migration and later upgrade Sourcegraph twice more, you may effectively "skip" an important migration.
 
-We're planning to improve this by having Sourcegraph notify you as a site admin when you should do the above, since today it is not actually required in most upgrades. See https://github.com/sourcegraph/sourcegraph/issues/4650 for details. In the meantime, we will do our best to communicate when this is needed to you through the changelog.
+We're planning to improve this by having Sourcegraph notify you as a site admin when you should do the above, since today it is not actually required in most upgrades. In the meantime, we will do our best to communicate when this is needed to you through the changelog.
 
 ## Kubernetes ConfigMap
 

docs/admin/config/batch_changes.mdx

@@ -60,7 +60,7 @@ You may encounter this error when publishing changesets to GitHub:
 
 In addition to their normal API rate limits, GitHub also has an internal _content creation_ limit (also called [secondary rate limit](https://docs.github.com/en/rest/guides/best-practices-for-integrators?apiVersion=2022-11-28#dealing-with-secondary-rate-limits)), which is an [intentional](https://github.com/cli/cli/issues/4801#issuecomment-1029207971) restriction on the platform to combat abuse by automated actors. At the time of writing, the specifics of this limit remain undocumented, due largely to the fact that it is dynamically determined (see [this GitHub issue](https://github.com/cli/cli/issues/4801)). However, the behavior of the limit is that it only permits a fixed number of resources to be created per minute and per hour, and exceeding this limit triggers a temporary hour-long suspension during which time no additional resources of this type can be created.
 
-Presently, Batch Changes does not automatically work around this limit feature request tracked [here](https://github.com/sourcegraph/sourcegraph/issues/44631). The current guidance if you do encounter this issue is to wait an hour and then try again, setting a less frequent `rolloutWindows` rate until this issue is no longer encountered.
+Presently, Batch Changes does not automatically work around this limit feature request. The current guidance if you do encounter this issue is to wait an hour and then try again, setting a less frequent `rolloutWindows` rate until this issue is no longer encountered.
 
 ### Rollout window object
 

docs/admin/deploy/docker-single-container/index.mdx

@@ -164,7 +164,7 @@ From sourcegraph version 5.11 onwards, the Sourcegraph single container Docker i
 
 `docker run --publish 7080:7080 --publish 127.0.0.1:3370:3370 --rm --volume ~/.sourcegraph/config:/etc/sourcegraph --volume ~/.sourcegraph/data:/var/opt/sourcegraph sourcegraph/server:{CURRENT_VERSION_NO_V}`
 
-You now have a single server Sourcegraph container image running on Postgresql 16. 
+You now have a single server Sourcegraph container image running on Postgresql 16.
 
 
 ### Standard upgrades
@@ -271,7 +271,7 @@ The version of this Postgres container is dependent on the version of the instan
 
 ## Troubleshooting
 
-If you get stuck or need help, [file an issue](https://github.com/sourcegraph/sourcegraph/issues/new?&title=Improve+Sourcegraph+quickstart+guide), [tweet (@sourcegraph)](https://twitter.com/sourcegraph) or [email](mailto:support@sourcegraph.com?subject=Sourcegraph%20quickstart%20guide).
+If you get stuck or need help, please reach out to [Sourcegraph support](https://help.sourcegraph.com/hc/en-us/requests/new).
 
 ### Mac Computers with Apple silicon
 

docs/admin/deploy/kubernetes/index.mdx

@@ -1107,7 +1107,7 @@ Some Persistent Volumes may be retained after the uninstall phase is complete. I
 [AWS EBS CSI driver]: https://docs.aws.amazon.com/eks/latest/userguide/managing-ebs-csi.html
 [NGINX Ingress Controller]: https://github.com/kubernetes/ingress-nginx
 [Helm Changelog]: https://github.com/sourcegraph/deploy-sourcegraph-helm/blob/main/charts/sourcegraph/CHANGELOG
-[Sourcegraph Changelog]: https://github.com/sourcegraph/sourcegraph-public-snapshot/blob/main/CHANGELOG
+[Sourcegraph Changelog]: https://sourcegraph.com/changelog
 [Sourcegraph Migrator]: https://github.com/sourcegraph/deploy-sourcegraph-helm/blob/main/charts/sourcegraph-migrator
 [Helm Diff]: https://github.com/databus23/helm-diff
 [Secrets]: https://kubernetes.io/docs/concepts/configuration/secret/

docs/admin/deploy/kubernetes/upgrade.mdx

@@ -183,7 +183,7 @@ To perform a multi-version upgrade via migrators [upgrade](/admin/updates/migrat
 
         Execution will continue, but please report this, along with your operating
         system, terminal, and any other details, to:
-          https://github.com/sourcegraph/sourcegraph/issues/new
+          https://sourcegraph.com/contact
 
      ✱ Sourcegraph migrator 4.5.1
      👉 Migrating to v3.43 (step 1 of 3)

docs/admin/deployment_best_practices.mdx

@@ -62,8 +62,9 @@ _It is possible to migrate your data to a Docker-Compose or Kubernetes deploymen
 
 Only the latest versions of IDEs are generally supported, but most versions within a few months up-to-date generally work.
 
-- VS Code: [https://github.com/sourcegraph/sourcegraph/tree/main/client/vscode](https://github.com/sourcegraph/sourcegraph/tree/main/client/vscode); we don't yet support VSCodium
-- JetBrains IDEs: [https://github.com/sourcegraph/sourcegraph/tree/main/client/jetbrains](https://github.com/sourcegraph/sourcegraph/tree/main/client/jetbrains) – we mainly test the plugin with IntelliJ IDEA, but it should work with no issues in all JetBrains IDEs, including:
+- VS Code
+- Visual Studio
+- JetBrains IDEs — we mainly test the plugin with IntelliJ IDEA, but it should work with no issues in all JetBrains IDEs, including:
   - IntelliJ IDEA
   - IntelliJ IDEA Community Edition
   - PhpStorm