From 47a6e4bccb8b0f83c69211bdc9301b3c5319d0f1 Mon Sep 17 00:00:00 2001
From: Erik Seliger <erikseliger@me.com>
Date: Sun, 26 Apr 2026 16:06:45 +0200
Subject: [PATCH 1/2] Cleanup and improve code search docs a bit

Read through some of these pages and noticed some things.
---
 docs/code-navigation/index.mdx               |  21 +-
 docs/code-navigation/troubleshooting.mdx     |  55 +++--
 docs/code-search/faq.mdx                     |  27 +--
 docs/code-search/features.mdx                |  11 -
 docs/code-search/how-to/index.mdx            |   3 +-
 docs/code-search/index.mdx                   |  28 +--
 docs/code-search/queries/index.mdx           |  45 ++---
 docs/code-search/queries/language.mdx        | 201 +++++++++----------
 docs/code-search/types/search-jobs.mdx       |  58 ++----
 docs/code-search/types/structural.mdx        |  25 ++-
 docs/code-search/types/symbol.mdx            |  18 +-
 docs/code-search/working/saved-searches.mdx  |  14 +-
 docs/code-search/working/search-contexts.mdx |  85 ++++----
 13 files changed, 266 insertions(+), 325 deletions(-)

diff --git a/docs/code-navigation/index.mdx b/docs/code-navigation/index.mdx
index 83444757b..56963f786 100644
--- a/docs/code-navigation/index.mdx
+++ b/docs/code-navigation/index.mdx
@@ -11,9 +11,9 @@ seoPriority: 1.0
 
 Code Navigation helps you quickly understand your code, its dependencies, and symbols within the Sourcegraph file view while making it easier to move through your codebase via:
 
--   Onboarding to codebases faster with cross-repository code navigation features like [Go to definition](/code-navigation/features#go-to-definition) and [Find references](/code-navigation/features#find-references)
--   Providing complete precise reviews, getting up to speed on unfamiliar code, and determining the impact of code changes with the confidence of compiler-accurate code navigation
--   Determining the root causes quickly with precise code navigation that tracks references across repositories and package dependencies
+- Onboarding to codebases faster with cross-repository code navigation features like [Go to definition](/code-navigation/features#go-to-definition) and [Find references](/code-navigation/features#find-references)
+- Providing complete precise reviews, getting up to speed on unfamiliar code, and determining the impact of code changes with the confidence of compiler-accurate code navigation
+- Determining the root causes quickly with precise code navigation that tracks references across repositories and package dependencies
 
 <video
 	width="1920"
@@ -66,13 +66,13 @@ Code Navigation helps you quickly understand your code, its dependencies, and sy
 
 Code Navigation helps you with the following tasks:
 
-| **Feature**                                                                         | **Description**                                                                                                                                                |
-| ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Feature**                                                            | **Description**                                                                                                                                                |
+| ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [Hover](/code-navigation/features#hover)                               | Quickly view a symbol's type signature and documentation without switching to another source file                                                              |
 | [Go to definition](/code-navigation/features#go-to-definition)         | Click the button or symbol name, navigates you to the symbol's definition                                                                                      |
 | [Find references](/code-navigation/features#find-references)           | Selecting it in the hover lists all references, definitions, and implementations at the bottom, including precise and search-based results                     |
 | [Find implementations](/code-navigation/features#find-implementations) | Click to go to a symbol's interface definition or, at the interface, see all implementations across repositories, including interfaces implemented by a struct |
-| [Perform an action](/code-navigation/features#perform-an-action)                    | When browsing code, you can perform a couple of actions like open in code host, raw download and view blame.                                                   |
+| [Perform an action](/code-navigation/features#perform-an-action)       | When browsing code, you can perform a couple of actions like open in code host, raw download and view blame.                                                   |
 
 <Callout type="note">
 	Read and learn more about [Code Navigation features here
@@ -83,10 +83,13 @@ Code Navigation helps you with the following tasks:
 
 There are two types of Code Navigation that Sourcegraph supports:
 
--   [Search-based Code Navigation](/code-navigation/search-based-code-navigation): Works out of the box with most popular programming languages, powered by Sourcegraph's code search. It uses a mix of text search and syntax-level heuristics (no language-level semantic information) for fast, performant searches across large code bases.
--   [Precise Code Navigation](/code-navigation/precise-code-navigation): Uses compile-time information to provide users with accurate cross-repository navigation experience across the entire code base.
-
+- [Search-based Code Navigation](/code-navigation/search-based-code-navigation): Works out of the box with most popular programming languages, powered by Sourcegraph's code search. It uses a mix of text search and syntax-level heuristics (no language-level semantic information) for fast, performant searches across large code bases.
+- [Precise Code Navigation](/code-navigation/precise-code-navigation): Uses compile-time information to provide users with accurate cross-repository navigation experience across the entire code base.
 
 ## Architecture
 
 Learn about how Code Navigation fits into Sourcegraph in the [architecture overview](/admin/architecture#code-navigation).
+
+## What languages are supported?
+
+Search-based code navigation supports 40 programming languages, including all of the most popular ones: Apex, Clojure, Cobol, C++, C#, CSS, Cuda, Dart, Elixir, Erlang, Go, GraphQL, Groovy, Haskell, Java, JavaScript, Jsonnet, Kotlin, Lisp, Lua, OCaml, Pascal, Perl, PHP, PowerShell, Protobuf, Python, R, Ruby, Rust, Scala, Shell, Starlark, Strato, Swift, Tcl, Thrift, TypeScript, Verilog, VHDL.
diff --git a/docs/code-navigation/troubleshooting.mdx b/docs/code-navigation/troubleshooting.mdx
index 3fa74214a..ced759403 100644
--- a/docs/code-navigation/troubleshooting.mdx
+++ b/docs/code-navigation/troubleshooting.mdx
@@ -11,17 +11,17 @@ Issues are related to Sourcegraph code navigation when the [indexer](/code-navig
 
 A customer issue should **definitely** be routed to code navigation if any of the following are true.
 
--   Precise code navigation queries are slow
--   Precise code navigation queries yield unexpected results
+- Precise code navigation queries are slow
+- Precise code navigation queries yield unexpected results
 
 A customer issue should **possibly** be routed to code navigation if any of the following are true.
 
--   Search-based code navigation queries are slow
--   Search-based code navigation queries yield unexpected results
+- Search-based code navigation queries are slow
+- Search-based code navigation queries yield unexpected results
 
 A customer issue should **not** be routed to code navigation if any of the following are true.
 
--   The indexer is listed in [LSIF.dev](https://lsif.dev/) and _it is not_ one that we maintain. Instead, flag the indexers status and maintainer of the relevant indexer with the customer, and suggest they reach out directly
+- The indexer is listed in [LSIF.dev](https://lsif.dev/) and _it is not_ one that we maintain. Instead, flag the indexers status and maintainer of the relevant indexer with the customer, and suggest they reach out directly
 
 ## Gathering evidence
 
@@ -31,24 +31,24 @@ Before bringing a code navigation issue to the engineering team, the site-admin
 
 The following details should always be supplied.
 
--   The Sourcegraph instance version
--   The Sourcegraph instance deployment type (e.g. server, pure-docker, docker-compose, k8s)
--   The memory, cpu, and disk resources allocated to the following containers:
-    -   frontend
-    -   precise-code-intel-worker
-    -   codeintel-db
-    -   blobstore (or `minio` in versions of Sourcegraph before v3.4.2)
+- The Sourcegraph instance version
+- The Sourcegraph instance deployment type (e.g. server, pure-docker, docker-compose, k8s)
+- The memory, cpu, and disk resources allocated to the following containers:
+    - frontend
+    - precise-code-intel-worker
+    - codeintel-db
+    - blobstore (or `minio` in versions of Sourcegraph before v3.4.2)
 
 If the customer is running a custom patch or an insiders version, we need the docker image tags and SHAs of the following containers:
 
--   frontend
--   precise-code-intel-worker
+- frontend
+- precise-code-intel-worker
 
 ### Sourcegraph CLI details
 
 The following details should be supplied if there is an issue with _uploading_ LSIF indexes to their instance.
 
--   The Sourcegraph CLI version
+- The Sourcegraph CLI version
 
 ```bash
 $ src version
@@ -60,13 +60,13 @@ Recommended Version: 3.26.1
 
 The following user settings should be supplied if there is an issue with _displaying_ code navigation results. Only these settings should be necessary, but additional settings can be supplied after private settings such as passwords or secret keys have been removed.
 
--   `codeIntel.lsif`
--   `codeIntel.traceExtension`
--   `codeIntel.disableRangeQueries`
--   `basicCodeIntel.includeForks`
--   `basicCodeIntel.includeArchives`
--   `basicCodeIntel.indexOnly`
--   `basicCodeIntel.unindexedSearchTimeout`
+- `codeIntel.lsif`
+- `codeIntel.traceExtension`
+- `codeIntel.disableRangeQueries`
+- `basicCodeIntel.includeForks`
+- `basicCodeIntel.includeArchives`
+- `basicCodeIntel.indexOnly`
+- `basicCodeIntel.unindexedSearchTimeout`
 
 You can get your effective user settings (site-config + user settings override) with the following Sourcegraph CLI command.
 
@@ -96,3 +96,14 @@ Hovering over identifiers in the source file should fire off requests to the API
 
 ![Network waterfall](https://storage.googleapis.com/sourcegraph-assets/Docs/network-waterfall.png)
 ![Request headers](https://storage.googleapis.com/sourcegraph-assets/Docs/network-description.png)
+
+## Why are my results sometimes incorrect?
+
+If an index is not found for a particular file in a repository, Sourcegraph will fall back to search-based code navigation. You may occasionally see results from search-based code navigation even when you have uploaded an index. This can happen in the following scenarios:
+
+The line containing the symbol was created or edited between the nearest indexed commit and the commit being browsed.
+The Find references panel may include search-based results, but only after all of the precise results have been displayed. This ensures every symbol has useful code navigation.
+
+### Why does it sometimes time out?
+
+The [symbol search](/code-search/types/symbol) performance section describes query paths and performance. Consider using [Rockskip](/code-navigation/rockskip) if you're experiencing frequent timeouts.
diff --git a/docs/code-search/faq.mdx b/docs/code-search/faq.mdx
index 5ddb8718a..f7a2deb22 100644
--- a/docs/code-search/faq.mdx
+++ b/docs/code-search/faq.mdx
@@ -8,11 +8,9 @@
 
 ### Does Code Search work with my repositories?
 
-Code Search works with all your repositories. Likewise, you can also [search through our public code](https://sourcegraph.com/search) that has a 2 million+ open source codebase.
+Code Search works with all your repositories, and scales with the biggest enterprises.
 
-### Who can search my code?
-
-Public code is searchable by anyone, but your private code can be searched only by users who have access to it.
+Likewise, you can also [search through 1 million+ open source codebases](https://sourcegraph.com/search).
 
 ### Do I need to enable Code Navigation?
 
@@ -20,25 +18,8 @@ No, the default search-based code navigation works out of the box without any co
 
 ### What is the max file size limit for Code Search?
 
-By default, files larger than **1 MB** are excluded from search results.
+By default, files larger than **1 MB** are excluded from search results. This limit is configurable.
 
 ### What programming languages are supported?
 
-Code Search supports almost all programming languages: Java, Python, Go, JavaScript, TypeScript, C#/C/C++, Swift, Objective-C, Kotlin, Ruby, Scala, Rust, Perl, Dart, Erlang, COBOL, Clojure, Lisp, Shell, Terraform, Lua, GraphQL, Thrift, Protobuf, YAML, JSON, Jsonnet, R, PHP, Elixir, Haskell, PowerShell, OCaml, CUDA, Pascal, Verilog, VHDL, Groovy, and Tcl.
-
-## Code Navigation
-
-## Why are my results sometimes incorrect?
-
-If an index is not found for a particular file in a repository, Sourcegraph will fall back to search-based code navigation. You may occasionally see results from search-based code navigation even when you have uploaded an index. This can happen in the following scenarios:
-
-The line containing the symbol was created or edited between the nearest indexed commit and the commit being browsed.
-The Find references panel may include search-based results, but only after all of the precise results have been displayed. This ensures every symbol has useful code navigation.
-
-## What languages are supported?
-
-Search-based code navigation supports 40 programming languages, including all of the most popular ones: Apex, Clojure, Cobol, C++, C#, CSS, Cuda, Dart, Elixir, Erlang, Go, GraphQL, Groovy, Haskell, Java, JavaScript, Jsonnet, Kotlin, Lisp, Lua, OCaml, Pascal, Perl, PHP, PowerShell, Protobuf, Python, R, Ruby, Rust, Scala, Shell, Starlark, Strato, Swift, Tcl, Thrift, TypeScript, Verilog, VHDL.
-
-### Why does it sometimes time out?
-
-The [symbol search](/code-search/types/symbol) performance section describes query paths and performance. Consider using [Rockskip](/code-navigation/rockskip) if you're experiencing frequent timeouts.
+Code Search supports almost programming languages, including: Java, Python, Go, JavaScript, TypeScript, C#/C/C++, Swift, Objective-C, Kotlin, Ruby, Scala, Rust, Perl, Dart, Erlang, COBOL, Clojure, Lisp, Shell, Terraform, Lua, GraphQL, Thrift, Protobuf, YAML, JSON, Jsonnet, R, PHP, Elixir, Haskell, PowerShell, OCaml, CUDA, Pascal, Verilog, VHDL, Groovy, and Tcl.
diff --git a/docs/code-search/features.mdx b/docs/code-search/features.mdx
index b86a4d8f3..0a0788188 100644
--- a/docs/code-search/features.mdx
+++ b/docs/code-search/features.mdx
@@ -98,17 +98,6 @@ src search --json --stream -- "/$re2_regex/" \
   ' --args "$pcre2_regex"
 ```
 
-## Search experience
-
-Users on Sourcegraph instance `v5.9.0` or more get the improved and new Code Search experience set by default. Sourcegraph Enterprise users' site admins can optionally opt-out and revert to the old view.
-
-You get the following improvements:
-
-- **In-line diff view**: Easily compare commits and see how a file changed over time, all in-line
-- **Revamped code navigation**: Quickly find a list of references of a given symbol, or immediately jump to the definition
-- **Reworked fuzzy finder ⌘K**: Find files and symbols quickly and easily with our whole new fuzzy finder
-- **File actions**: Like open in editor and open on code host
-
 ## Personalized search ranking
 
 Sourcegraph Enterprise users can get more personalized and better-ranked search results in the search bar for their codebases. With this feature, you get:
diff --git a/docs/code-search/how-to/index.mdx b/docs/code-search/how-to/index.mdx
index 3b6d68f18..e384753f2 100644
--- a/docs/code-search/how-to/index.mdx
+++ b/docs/code-search/how-to/index.mdx
@@ -1,4 +1,3 @@
 # How-to guides
 
--   [Switch from Oracle OpenGrok to Sourcegraph](/code-search/how-to/opengrok)
--   [How to create a search context with the GraphQL API](/api/graphql)
+- [Switch from Oracle OpenGrok to Sourcegraph](/code-search/how-to/opengrok)
diff --git a/docs/code-search/index.mdx b/docs/code-search/index.mdx
index 35ee97cc6..821d04b8a 100644
--- a/docs/code-search/index.mdx
+++ b/docs/code-search/index.mdx
@@ -34,9 +34,9 @@ seoPriority: 1.0
 
 Sourcegraph's Code Search empowers you to:
 
--   Utilize regular expressions, boolean operations, and keyboard shortcuts to help you unleash the full potential of your searches
--   With the symbol, commit, and diff search capabilities, it identifies code vulnerabilities in milliseconds and quickly helps you resolve issues and incidents
--   Offers innovative code view with seamless code navigation for a comprehensive coding experience
+- Utilize regular expressions, boolean operations, and keyboard shortcuts to help you unleash the full potential of your searches
+- With the symbol, commit, and diff search capabilities, it identifies code vulnerabilities in milliseconds and quickly helps you resolve issues and incidents
+- Offers innovative code view with seamless code navigation for a comprehensive code understanding experience
 
 ## Getting started
 
@@ -88,26 +88,26 @@ Sourcegraph's Code Search empowers you to:
 
 Code Search main features include:
 
--   Use [query assist](/code-search/query-assist) to search with natural language
--   Use regular expressions and keyword queries to perform full-text searches
--   Search any branch and commit, with no indexing required
--   Search [commit diffs](/code-search/features#commit-diff-search) and [commit messages](/code-search/features#commit-message-search) to see how code has changed
--   Narrow your search by repository and file pattern
--   Use [search contexts](/code-search/features#search-contexts) to search across a set of repositories at specific revisions
--   Curate [saved searches](/code-search/features#saved-searches) for yourself or your org
--   Use [code monitoring](/code-monitoring/) to set up notifications for code changes that match a query
--   View [language statistics](/code-search/features#statistics) for search results
+- Use [query assist](/code-search/query-assist) to search with natural language
+- Use regular expressions and keyword queries to perform full-text searches
+- Search any branch and commit, with no indexing required
+- Search [commit diffs](/code-search/features#commit-diff-search) and [commit messages](/code-search/features#commit-message-search) to see how code has changed
+- Narrow your search by repository and file pattern
+- Use [search contexts](/code-search/features#search-contexts) to search across a set of repositories at specific revisions
+- Curate [saved searches](/code-search/features#saved-searches) for yourself or your org
+- Use [code monitoring](/code-monitoring/) to set up notifications for code changes that match a query
+- View [language statistics](/code-search/features#statistics) for search results
 
 <Callout type="note">
 	{' '}
-	Read more in detail about the [Code Search features here →](/code-search/features)
+	Read more in detail about the [Code Search features here
+	→](/code-search/features)
 </Callout>
 
 <Callout type="note">
 	Check out the [Code Search FAQs here →](/code-search/faq)
 </Callout>
 
-
 ## Architecture
 
 Learn about how Code Search fits into Sourcegraph in the [architecture overview](/admin/architecture#code-search).
diff --git a/docs/code-search/queries/index.mdx b/docs/code-search/queries/index.mdx
index b8dfa9f3b..5d8ad434d 100644
--- a/docs/code-search/queries/index.mdx
+++ b/docs/code-search/queries/index.mdx
@@ -6,8 +6,8 @@
 
 A typical search consists of two parts:
 
--   A [search pattern](#search-patterns) containing the terms you want to search, for example `println`
--   [Search filters](#filters-all-searches) that scope the search to certain repositories, languages, etc., for example `lang:java`
+- A [search pattern](#search-patterns) containing the terms you want to search, for example `println`
+- [Search filters](#filters-all-searches) that scope the search to certain repositories, languages, etc., for example `lang:java`
 
 For a graphical view of Sourcegraph's query syntax, see the [search language reference](/code-search/queries/language).
 
@@ -42,9 +42,9 @@ Clicking the (.\*) toggle interprets all search patterns as regular expressions.
 <Callout type="note">
 	{' '}
 	In [Keyword search](#keyword-search-default), use `/.../` to perform regular
-	expression searches. Use this mode if you prefer writing out regular expressions
-	without enclosing them. In this mode spaces between patterns mean **match anything**.
-	Patterns inside quotes mean **match exactly**.
+	expression searches. Use this mode if you prefer writing out regular
+	expressions without enclosing them. In this mode spaces between patterns
+	mean **match anything**. Patterns inside quotes mean **match exactly**.
 </Callout>
 
 | **Search Syntax**                                                                                                                                            | **Description**                                                                                                                              |
@@ -79,13 +79,13 @@ The following filters can be used on all searches (using [RE2 syntax](https://go
 | **case:yes**                                                                                                                                                                                                                                                     | Perform a case sensitive query. Without this, everything is matched case insensitively                                                                                                                                                                                                                                                                                                                                                               | [`OPEN_FILE case:yes`](https://sourcegraph.com/search?q=OPEN_FILE+case:yes)                                                                                                                                                                                                                                                                                                         |
 | **fork:yes, fork:only**                                                                                                                                                                                                                                          | Include results from repository forks or filter results to only repository forks. Results in repository forks are excluded by default                                                                                                                                                                                                                                                                                                                | [`fork:yes repo:sourcegraph`](https://sourcegraph.com/search?q=fork:yes+repo:sourcegraph)                                                                                                                                                                                                                                                                                           |
 | **archived:yes, archived:only**                                                                                                                                                                                                                                  | The yes option, includes archived repositories. The only option, filters results to only archived repositories. Results in archived repositories are excluded by default                                                                                                                                                                                                                                                                             | [`repo:sourcegraph/ archived:only`](https://sourcegraph.com/search?q=repo:%5Egithub.com/sourcegraph/+archived:only)                                                                                                                                                                                                                                                                 |
-| **repo:has.meta(...)**                                                                                                                                                                                                                                           | Conditionally search inside repositories only if they are associated with a specified metadata: <br /> 1. key-value pair, or<br /> 2. key with any value, or <br />3. key with no value <br />See [built-in predicates](/code-search/queries/language#built-in-repo-predicate) for more                                                                                                                                             | 1. `repo:has.meta(owning-team:security)` <br /> 2. `repo:has.meta(owning-team)` <br /> 3. `repo:has.meta(archived:)`                                                                                                                                                                                                                                                                |
+| **repo:has.meta(...)**                                                                                                                                                                                                                                           | Conditionally search inside repositories only if they are associated with a specified metadata: <br /> 1. key-value pair, or<br /> 2. key with any value, or <br />3. key with no value <br />See [built-in predicates](/code-search/queries/language#built-in-repo-predicate) for more                                                                                                                                                              | 1. `repo:has.meta(owning-team:security)` <br /> 2. `repo:has.meta(owning-team)` <br /> 3. `repo:has.meta(archived:)`                                                                                                                                                                                                                                                                |
 | **repo:has.path(...)**                                                                                                                                                                                                                                           | Conditionally search inside repositories only if they contain a file path matching the regular expression. See [built-in predicates](/code-search/queries/language#built-in-repo-predicate) for more                                                                                                                                                                                                                                                 | [`repo:has.path(\.py) file:Dockerfile pip`](https://sourcegraph.com/search?q=context:global+repo:has.path%28%5C.py%29+file:Dockerfile+pip&patternType=keyword)                                                                                                                                                                                                                      |
 | **repo:has.topic(...)**                                                                                                                                                                                                                                          | Search only in repos repositories if they have the given GitHub or GitLab topic. See [built-in predicates](/code-search/queries/language#built-in-repo-predicate) for more                                                                                                                                                                                                                                                                           | [`repo:has.topic(code-search) rank`](https://sourcegraph.com/search?q=context:global+repo:sourcegraph/sourcegraph%24+rank&patternType=keyword&sm=1&groupBy=repo)                                                                                                                                                                                                                    |
 | **repo:has.commit.after(...)**                                                                                                                                                                                                                                   | Filter out stale repositories that don't contain commits past the specified time frame. See [built-in predicates](/code-search/queries/language#built-in-repo-predicate) for more                                                                                                                                                                                                                                                                    | [`repo:has.commit.after(yesterday)`](https://sourcegraph.com/search?q=context:global+repo:.*sourcegraph.*+repo:has.commit.after%28yesterday%29&patternType=keyword) <br /> [`repo:has.commit.after(june 25 2017)`](https://sourcegraph.com/search?q=context:global+repo:.*sourcegraph.*+repo:has.commit.after%28june+25+2017%29&patternType=keyword)                                |
 | **rev:at.time(...)**                                                                                                                                                                                                                                             | Search a repo or a branch at a specific point in time.                                                                                                                                                                                                                                                                                                                                                                                               | [`rev:at.time(1 year ago)`](https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:at.time%281+year+ago%29+&patternType=keyword&sm=0) <br /> [`rev:at.time(2021-01-01)`](https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:at.time%282021-01-01%2C+v5.0.0%29+&patternType=keyword) |
 | **file:has.content(...)**                                                                                                                                                                                                                                        | Conditionally search files only if they contain contents that match the provided regex pattern. See [built-in predicates](/code-search/queries/language#built-in-repo-predicate) for more                                                                                                                                                                                                                                                            | [`file:has.content(Copyright) Sourcegraph`](https://sourcegraph.com/search?q=context:global+file:has.content%28Copyright%29+Sourcegraph&patternType=keyword)                                                                                                                                                                                                                        |
-| **file:has.owners(...)**                                                                                                                                                                                                                                         | Conditionally search files only if they are owned by the given owner. Empty means _any owner_. See [code ownership documentation](/code-ownership) for more                                                                                                                                                                                                                                                                                            | [`file:has.owner(alice@sourcegraph.com) Sourcegraph`](https://sourcegraph.com/search?q=context:global+file:has.owner%28alice@sourcegraph.com%29+Sourcegraph&patternType=keyword)                                                                                                                                                                                                    |
+| **file:has.owners(...)**                                                                                                                                                                                                                                         | Conditionally search files only if they are owned by the given owner. Empty means _any owner_. See [code ownership documentation](/code-ownership) for more                                                                                                                                                                                                                                                                                          | [`file:has.owner(alice@sourcegraph.com) Sourcegraph`](https://sourcegraph.com/search?q=context:global+file:has.owner%28alice@sourcegraph.com%29+Sourcegraph&patternType=keyword)                                                                                                                                                                                                    |
 | **file:has.contributor(...)**                                                                                                                                                                                                                                    | Conditionally search files only if a file contributor's name or email matches the provided regex pattern. See [built-in predicates](/code-search/queries/language#built-in-file-predicate) for more                                                                                                                                                                                                                                                  | [`file:has.contributor(alice@sourcegraph.com) Sourcegraph`](https://sourcegraph.com/search?q=context:global+file:has.owner%28alice@sourcegraph.com%29+Sourcegraph&patternType=keyword)                                                                                                                                                                                              |
 | **count:_N_,< /> count:all**                                                                                                                                                                                                                                     | Retrieve <em>N</em> results. By default, Sourcegraph stops searching early and returns if it finds a full page of results. This is desirable for most interactive searches. To wait for all results, use **count:all**                                                                                                                                                                                                                               | [`count:1000 function`](https://sourcegraph.com/search?q=count:1000+repo:sourcegraph/sourcegraph$+function) <br /> [`count:all err`](https://sourcegraph.com/search?q=repo:github.com/sourcegraph/sourcegraph+err+count:all&patternType=keyword)                                                                                                                                    |
 | **timeout:_go-duration-value_**                                                                                                                                                                                                                                  | Customizes the timeout for searches. The value of the parameter is a string that can be parsed by the [Go time package's `ParseDuration`](https://golang.org/pkg/time/#ParseDuration) (e.g. 10s, 100ms). By default, the timeout is set to 10 seconds, and the search will optimize for returning results as soon as possible. The timeout value cannot be set longer than 1 minute. When provided, the search is given the full timeout to complete | [`repo:^github.com/sourcegraph timeout:15s func count:10000`](https://sourcegraph.com/search?q=repo:%5Egithub.com/sourcegraph/+timeout:15s+func+count:10000)                                                                                                                                                                                                                        |
@@ -94,11 +94,6 @@ The following filters can be used on all searches (using [RE2 syntax](https://go
 
 Multiple or combined **repo:** and **file:** filters are intersected. For example, `repo:foo repo:bar` limits your search to repositories whose path contains **both** `foo` and `bar` (such as `github.com/alice/foobar`). To include results from repositories whose path contains **either** `foo` or `bar`, use `repo:foo|bar`.
 
-<Callout type="info">
-	The `rev:at.time(...)` filter is only supported for Sourcegraph versions 5.4
-	or more.
-</Callout>
-
 ## Boolean operators
 
 Use boolean operators to create more expressive searches.
@@ -125,8 +120,8 @@ search patterns, `NOT` excludes documents that contain the term after `NOT`. For
 
 <Callout type="note">
 	{' '}
-	If you want to search for reserved keywords like `OR` in your code use `content`
-	like this: `content:"query with OR"`.
+	If you want to search for reserved keywords like `OR` in your code use
+	`content` like this: `content:"query with OR"`.
 </Callout>
 
 ### Operator precedence and groups
@@ -180,9 +175,9 @@ revisions (branches, commit hashes, and tags) and may take on the following form
 
 (All examples apply to `@` as well as `rev:`)
 
--   `@branch` - a branch name
--   `@1735d48` - a commit hash
--   `@3.15` - a tag
+- `@branch` - a branch name
+- `@1735d48` - a commit hash
+- `@3.15` - a tag
 
 You can separate revisions by a colon to search multiple revisions at the same time, `@branch:1735d48:3.15`.
 
@@ -193,22 +188,22 @@ with `3.18`, but not a branch called `3.18` and vice versa for `@refs/heads/3.18
 **Glob patterns** allow you to search over a range of branches or tags. Prepend `*` to mark a revision
 as glob pattern and add the glob-pattern after it like this `repo:<repo>@*<glob-pattern>`. For example:
 
--   [`@*refs/heads/*`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/docker/machine%24%40*refs/heads/*+middleware&patternType=keyword) - search across all branches
--   [`@*refs/tags/*`](https://sourcegraph.com/search?q=repo:github.com/docker/machine%24%40*refs/tags/*+server&patternType=keyword) - search across all tags
+- [`@*refs/heads/*`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/docker/machine%24%40*refs/heads/*+middleware&patternType=keyword) - search across all branches
+- [`@*refs/tags/*`](https://sourcegraph.com/search?q=repo:github.com/docker/machine%24%40*refs/tags/*+server&patternType=keyword) - search across all tags
 
 We automatically add a trailing `/*` if it is missing from the glob pattern.
 
 You can negate a glob pattern by prepending `*!`, for example:
 
--   [`@*refs/heads/*:*!refs/heads/release* type:commit `](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/kubernetes/kubernetes%24%40*refs/heads/*:*%21refs/heads/release*+type:commit+&patternType=keyword) - search commits on all branches except on those that start with "release"
--   [`@*refs/tags/v3.*:*!refs/tags/v3.*-* context`](https://sourcegraph.com/search?q=repo:%5Egithub.com/sourcegraph/sourcegraph%24%40*refs/tags/v3.*:*%21refs/tags/v3.*-*+context&patternType=keyword) - search all versions starting with `3.` except release candidates, alpha and beta versions.
+- [`@*refs/heads/*:*!refs/heads/release* type:commit `](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/kubernetes/kubernetes%24%40*refs/heads/*:*%21refs/heads/release*+type:commit+&patternType=keyword) - search commits on all branches except on those that start with "release"
+- [`@*refs/tags/v3.*:*!refs/tags/v3.*-* context`](https://sourcegraph.com/search?q=repo:%5Egithub.com/sourcegraph/sourcegraph%24%40*refs/tags/v3.*:*%21refs/tags/v3.*-*+context&patternType=keyword) - search all versions starting with `3.` except release candidates, alpha and beta versions.
 
 ### Repository names
 
 A query with only `repo:` filters returns a list of repositories with matching names.
 
--   Example: [`repo:docker repo:registry`](https://sourcegraph.com/search?q=repo:docker+repo:registry) matches repositories with names that contain both `docker` and `registry` substrings
--   Example: [`repo:docker OR repo:registry`](https://sourcegraph.com/search?q=repo:docker+OR+repo:registry&patternType=keyword) matches repositories with names that contain either `docker` or `registry` substrings
+- Example: [`repo:docker repo:registry`](https://sourcegraph.com/search?q=repo:docker+repo:registry) matches repositories with names that contain both `docker` and `registry` substrings
+- Example: [`repo:docker OR repo:registry`](https://sourcegraph.com/search?q=repo:docker+OR+repo:registry&patternType=keyword) matches repositories with names that contain either `docker` or `registry` substrings
 
 ### Commit and Diff searches
 
@@ -224,10 +219,10 @@ minus the commits reachable from the commit tagged with `3.15`.
 
 A query with `type:path` restricts terms to matching filenames only (not file contents).
 
--   Example: [`type:path repo:/docker/ registry`](https://sourcegraph.com/search?q=type:path+repo:/docker/+registry)
+- Example: [`type:path repo:/docker/ registry`](https://sourcegraph.com/search?q=type:path+repo:/docker/+registry)
 
 ## Content Search
 
 A query with `type:file` restricts terms to matching file contents only (not filenames).
 
--   Example: [`type:file repo:^github\.com/sourcegraph/about$ website`](https://sourcegraph.com/search?q=type:file+repo:%5Egithub%5C.com/sourcegraph/about%24+website&patternType=keyword)
+- Example: [`type:file repo:^github\.com/sourcegraph/about$ website`](https://sourcegraph.com/search?q=type:file+repo:%5Egithub%5C.com/sourcegraph/about%24+website&patternType=keyword)
diff --git a/docs/code-search/queries/language.mdx b/docs/code-search/queries/language.mdx
index 97813a0c7..c4dc0cf17 100644
--- a/docs/code-search/queries/language.mdx
+++ b/docs/code-search/queries/language.mdx
@@ -21,7 +21,7 @@ At a basic level, a query consists of [search patterns](#search-pattern) and [pa
 
 For example,
 
--   [`repo:github.com/sourcegraph/sourcegraph file:schema.graphql The result`](https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+file:schema.graphql+%22The+result%22&patternType=keyword)
+- [`repo:github.com/sourcegraph/sourcegraph file:schema.graphql The result`](https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+file:schema.graphql+%22The+result%22&patternType=keyword)
 
 ## Expression
 
@@ -31,7 +31,7 @@ Build query expressions by combining [basic queries](#basic-query) and operators
 
 For example,
 
--   [`repo:github.com/sourcegraph/sourcegraph rtr AND newRouter`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rtr+AND+newRouter&patternType=keyword)
+- [`repo:github.com/sourcegraph/sourcegraph rtr AND newRouter`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rtr+AND+newRouter&patternType=keyword)
 
 ## Search pattern
 
@@ -43,8 +43,8 @@ Perform a [regular expression search](/code-search/queries#regular-expression-se
 
 For example,
 
--   [`foo.*bar.*baz`](https://sourcegraph.com/search?q=foo.*bar.*baz&patternType=regexp)
--   [`"foo bar"`](https://sourcegraph.com/search?q=%22foo+bar%22&patternType=regexp)
+- [`foo.*bar.*baz`](https://sourcegraph.com/search?q=foo.*bar.*baz&patternType=regexp)
+- [`"foo bar"`](https://sourcegraph.com/search?q=%22foo+bar%22&patternType=regexp)
 
 ## Parameter
 
@@ -60,8 +60,8 @@ Search repositories that match the regular expression. A `-` before `repo` exclu
 
 For example,
 
--   [`repo:gorilla/mux testroute`](https://sourcegraph.com/search?q=repo:gorilla/mux+testroute&patternType=regexp)
--   [`-repo:gorilla/mux testroute`](https://sourcegraph.com/search?q=-repo:gorilla/mux+testroute&patternType=regexp)
+- [`repo:gorilla/mux testroute`](https://sourcegraph.com/search?q=repo:gorilla/mux+testroute&patternType=regexp)
+- [`-repo:gorilla/mux testroute`](https://sourcegraph.com/search?q=-repo:gorilla/mux+testroute&patternType=regexp)
 
 ### Revision
 
@@ -71,28 +71,24 @@ Search a repository at a given revision, for example, a branch name, commit hash
 
 For example,
 
--   [`repo:^github\.com/sourcegraph/sourcegraph$@75ba004 get_embeddings`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24%4075ba004+get_embeddings+&patternType=keyword)
--   [`repo:^github\.com/sourcegraph/sourcegraph$ rev:v5.0.0 get_embeddings`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:v5.0.0+get_embeddings&patternType=keyword)
+- [`repo:^github\.com/sourcegraph/sourcegraph$@75ba004 get_embeddings`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24%4075ba004+get_embeddings+&patternType=keyword)
+- [`repo:^github\.com/sourcegraph/sourcegraph$ rev:v5.0.0 get_embeddings`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:v5.0.0+get_embeddings&patternType=keyword)
 
 You can search multiple revisions by separating the revisions with `:`. Specify `HEAD` for the default branch.
 
 For example,
 
--   [`repo:^github\.com/sourcegraph/sourcegraph$ rev:v4.5.0:v5.0.0 disableNonCriticalTelemetry`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:v4.5.0:v5.0.0+disableNonCriticalTelemetry&patternType=keyword)
--   [`repo:^github\.com/sourcegraph/sourcegraph$@v4.5.0:v5.0.0 disableNonCriticalTelemetry`](https://sourcegraph.com/search?q=context%3Aglobal+repo%3A%5Egithub%5C.com%2Fsourcegraph%2Fsourcegraph%24%40v4.5.0%3Av5.0.0+disableNonCriticalTelemetry&patternType=keyword)
+- [`repo:^github\.com/sourcegraph/sourcegraph$ rev:v4.5.0:v5.0.0 disableNonCriticalTelemetry`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:v4.5.0:v5.0.0+disableNonCriticalTelemetry&patternType=keyword)
+- [`repo:^github\.com/sourcegraph/sourcegraph$@v4.5.0:v5.0.0 disableNonCriticalTelemetry`](https://sourcegraph.com/search?q=context%3Aglobal+repo%3A%5Egithub%5C.com%2Fsourcegraph%2Fsourcegraph%24%40v4.5.0%3Av5.0.0+disableNonCriticalTelemetry&patternType=keyword)
 
 ### Revision at time
 
-<Callout type="info">
-	This feature is only supported for Sourcegraph versions 5.4 or more.
-</Callout>
-
 Search a repository at a given time. Optionally, a second parameter can be used to specify a revision which will be used as the starting point of the search.
 
 For example,
 
--   [`repo:^github\.com/sourcegraph/sourcegraph$ rev:at.time(2 years ago) handbook`](https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:at.time%282+years+ago%29+handbook&patternType=keyword&sm=0)
--   [`repo:^github\.com/sourcegraph/sourcegraph$ rev:at.time(2021-01-30, v5.0.0) popular`](https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:at.time%282021-01-30%2C+v5.0.0%29+popular&patternType=keyword&sm=0)
+- [`repo:^github\.com/sourcegraph/sourcegraph$ rev:at.time(2 years ago) handbook`](https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:at.time%282+years+ago%29+handbook&patternType=keyword&sm=0)
+- [`repo:^github\.com/sourcegraph/sourcegraph$ rev:at.time(2021-01-30, v5.0.0) popular`](https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+rev:at.time%282021-01-30%2C+v5.0.0%29+popular&patternType=keyword&sm=0)
 
 ### File
 
@@ -102,8 +98,8 @@ Search files whose full path matches the regular expression. A `-` before `file`
 
 For example,
 
--   [`file:\.js$ httptest`](https://sourcegraph.com/search?q=file:%5C.js%24+httptest&patternType=regexp)
--   [`file:\.js$ -file:test http`](https://sourcegraph.com/search?q=file:%5C.js%24+-file:test+http&patternType=regexp)
+- [`file:\.js$ httptest`](https://sourcegraph.com/search?q=file:%5C.js%24+httptest&patternType=regexp)
+- [`file:\.js$ -file:test http`](https://sourcegraph.com/search?q=file:%5C.js%24+-file:test+http&patternType=regexp)
 
 ### Language
 
@@ -113,7 +109,7 @@ Only search files in the specified programming language, like `typescript` or `p
 
 For example,
 
--   [`lang:typescript encoding`](https://sourcegraph.com/search?q=lang:typescript+encoding&patternType=regexp)
+- [`lang:typescript encoding`](https://sourcegraph.com/search?q=lang:typescript+encoding&patternType=regexp)
 
 #### Content-based language detection (Beta)
 
@@ -132,7 +128,7 @@ Set the search pattern to search using a dedicated parameter. Useful, for exampl
 
 For example,
 
--   [`repo:sourcegraph content:"repo:sourcegraph"`](https://sourcegraph.com/search?q=repo:sourcegraph+content:%22repo:sourcegraph%22&patternType=keyword)
+- [`repo:sourcegraph content:"repo:sourcegraph"`](https://sourcegraph.com/search?q=repo:sourcegraph+content:%22repo:sourcegraph%22&patternType=keyword)
 
 ### Select
 
@@ -146,8 +142,8 @@ A query like `type:commit example select:symbol` will return no results because
 
 For example,
 
--   [`fmt.Errorf select:repo`](https://sourcegraph.com/search?q=fmt.Errorf+select:repo&patternType=keyword)
--   [`zoektSearch select:file`](https://sourcegraph.com/search?q=zoektSearch+select:file&patternType=keyword)
+- [`fmt.Errorf select:repo`](https://sourcegraph.com/search?q=fmt.Errorf+select:repo&patternType=keyword)
+- [`zoektSearch select:file`](https://sourcegraph.com/search?q=zoektSearch+select:file&patternType=keyword)
 
 #### Symbol kind
 
@@ -157,7 +153,7 @@ Select a specific kind of symbol. For example `type:symbol select:symbol.functio
 
 For example,
 
--   [`type:symbol zoektSearch select:symbol.function`](https://sourcegraph.com/search?q=type:symbol+zoektSearch+select:symbol.function&patternType=keyword)
+- [`type:symbol zoektSearch select:symbol.function`](https://sourcegraph.com/search?q=type:symbol+zoektSearch+select:symbol.function&patternType=keyword)
 
 #### Modified lines
 
@@ -172,7 +168,7 @@ When searching commit diffs, select only diffs where the pattern matches on `add
 
 For example,
 
--   [`repo:^github\.com/sourcegraph/sourcegraph$ type:diff TODO select:commit.diff.removed`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+type:diff+TODO+select:commit.diff.removed+&patternType=keyword)
+- [`repo:^github\.com/sourcegraph/sourcegraph$ type:diff TODO select:commit.diff.removed`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+type:diff+TODO+select:commit.diff.removed+&patternType=keyword)
 
 #### File kind
 
@@ -184,7 +180,7 @@ Select only directory paths of file results with `select:file.directory`. This i
 
 For example,
 
--   [`file:package\.json select:file.directory`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+file:package%5C.json+select:file.directory&patternType=keyword)
+- [`file:package\.json select:file.directory`](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+file:package%5C.json+select:file.directory&patternType=keyword)
 
 #### File owners
 
@@ -202,8 +198,8 @@ Set whether the search pattern should perform a search of a certain type. Notabl
 
 For example,
 
--   [`type:symbol path`](https://sourcegraph.com/search?q=type:symbol+path)
--   [`type:commit author:nick`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph%24+type:commit+author:nick&patternType=regexp)
+- [`type:symbol path`](https://sourcegraph.com/search?q=type:symbol+path)
+- [`type:commit author:nick`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph%24+type:commit+author:nick&patternType=regexp)
 
 ### Case
 
@@ -213,7 +209,7 @@ Set whether the search pattern should be treated case-sensitively. This is synon
 
 For example,
 
--   [`OPEN_FILE case:yes`](https://sourcegraph.com/search?q=OPEN_FILE+case:yes)
+- [`OPEN_FILE case:yes`](https://sourcegraph.com/search?q=OPEN_FILE+case:yes)
 
 ### Fork
 
@@ -223,7 +219,7 @@ Set to `yes` if repository forks should be included or `only` if only forks shou
 
 For example,
 
--   [`fork:yes repo:sourcegraph`](https://sourcegraph.com/search?q=fork:yes+repo:sourcegraph&patternType=regexp)
+- [`fork:yes repo:sourcegraph`](https://sourcegraph.com/search?q=fork:yes+repo:sourcegraph&patternType=regexp)
 
 ### Archived
 
@@ -233,7 +229,7 @@ Set to `yes` if archived repositories should be included or `only` if only archi
 
 For example,
 
--   [`archived:only repo:sourcegraph`](https://sourcegraph.com/search?q=archived:only+repo:sourcegraph&patternType=regexp)
+- [`archived:only repo:sourcegraph`](https://sourcegraph.com/search?q=archived:only+repo:sourcegraph&patternType=regexp)
 
 ### Count
 
@@ -243,8 +239,8 @@ Retrieve N results. By default, Sourcegraph stops searching early and returns if
 
 For example,
 
--   [`count:1000 function`](https://sourcegraph.com/search?q=count:1000+repo:sourcegraph/sourcegraph%24+function&patternType=regexp)
--   [`count:all err`](https://sourcegraph.com/search?q=repo:github.com/sourcegraph/sourcegraph+err+count:all&patternType=keyword)
+- [`count:1000 function`](https://sourcegraph.com/search?q=count:1000+repo:sourcegraph/sourcegraph%24+function&patternType=regexp)
+- [`count:all err`](https://sourcegraph.com/search?q=repo:github.com/sourcegraph/sourcegraph+err+count:all&patternType=keyword)
 
 ### Timeout
 
@@ -255,18 +251,20 @@ returning results as soon as possible. The timeout value cannot be set to longer
 
 For example,
 
--   [`timeout:15s count:10000 func`](https://sourcegraph.com/search?q=repo:%5Egithub.com/sourcegraph/+timeout:15s+func+count:10000) sets a longer timeout for a search that contains a lot of results.
+- [`timeout:15s count:10000 func`](https://sourcegraph.com/search?q=repo:%5Egithub.com/sourcegraph/+timeout:15s+func+count:10000) sets a longer timeout for a search that contains a lot of results.
 
 Sourcegraph admins can increase the maximum timeout of 1 minute through [site configuration](/admin/search#maximum-timeout).
 
 <Callout type="note">
-	The maximum timeout also depends on the HTTP load balancer or ingress controller
-	in front of Sourcegraph (nginx/ELB/Cloudflare/etc). Sourcegraph admins must ensure
-	timeouts for the `.api/search/stream` path are set to at least **5 minutes**, as
-	this endpoint uses [SSE](https://en.wikipedia.org/wiki/Server-sent_events) for
-	streaming search results. This requirement also applies to [Deep Search](/deep-search).
-	See the [Kubernetes deployment guide](/self-hosted/deploy/kubernetes#cloud-providers-guides)
-	for further guidance.
+	The maximum timeout also depends on the HTTP load balancer or ingress
+	controller in front of Sourcegraph (nginx/ELB/Cloudflare/etc). Sourcegraph
+	admins must ensure timeouts for the `.api/search/stream` path are set to at
+	least **5 minutes**, as this endpoint uses
+	[SSE](https://en.wikipedia.org/wiki/Server-sent_events) for streaming search
+	results. This requirement also applies to [Deep Search](/deep-search). See
+	the [Kubernetes deployment
+	guide](/self-hosted/deploy/kubernetes#cloud-providers-guides) for further
+	guidance.
 </Callout>
 
 ### Visibility
@@ -277,7 +275,7 @@ Filter results to only public or private repositories. The default is to include
 
 For example,
 
--   [`type:repo visibility:public`](https://sourcegraph.com/search?q=type:repo+visibility:public&patternType=regexp)
+- [`type:repo visibility:public`](https://sourcegraph.com/search?q=type:repo+visibility:public&patternType=regexp)
 
 ### Pattern type
 
@@ -299,9 +297,9 @@ Search only inside repositories that are associated with the provided key-value
 
 For example,
 
--   [`repo:has.meta(team:sourcegraph)`](https://sourcegraph.com/search?q=context:global+repo:has.meta%28team:sourcegraph%29&patternType=regexp&sm=1&groupBy=repo)
--   [`repo:has.meta(team:/[source]{5}graph/)`](https://sourcegraph.com/search?q=context:global+repo:has.meta%28team:/%5Bsource%5D%7B5%7Dgraph/%29&patternType=regexp&sm=1)
--   [`repo:has.meta(language)`](https://sourcegraph.com/search?q=context%3Aglobal+repo%3Ahas.meta%28language%29&patternType=regexp&sm=1&groupBy=repo)
+- [`repo:has.meta(team:sourcegraph)`](https://sourcegraph.com/search?q=context:global+repo:has.meta%28team:sourcegraph%29&patternType=regexp&sm=1&groupBy=repo)
+- [`repo:has.meta(team:/[source]{5}graph/)`](https://sourcegraph.com/search?q=context:global+repo:has.meta%28team:/%5Bsource%5D%7B5%7Dgraph/%29&patternType=regexp&sm=1)
+- [`repo:has.meta(language)`](https://sourcegraph.com/search?q=context%3Aglobal+repo%3Ahas.meta%28language%29&patternType=regexp&sm=1&groupBy=repo)
 
 ### Repo has file and content
 
@@ -311,7 +309,7 @@ Search only inside repositories that contain a file matching the `path:` with `c
 
 For example,
 
--   [`repo:has.file(path:CHANGELOG content:fix)`](https://sourcegraph.com/search?q=context:global+repo:github%5C.com/sourcegraph/.*+repo:has.file%28path:CHANGELOG+content:fix%29&patternType=keyword)
+- [`repo:has.file(path:CHANGELOG content:fix)`](https://sourcegraph.com/search?q=context:global+repo:github%5C.com/sourcegraph/.*+repo:has.file%28path:CHANGELOG+content:fix%29&patternType=keyword)
 
 <Callout type="note">
 	`repo:contains.file(...)` is an alias for `repo:has.file(...)` and behaves
@@ -326,11 +324,12 @@ Search only inside repositories that contain a file path matching the regular ex
 
 For example,
 
--   [`repo:has.path(README)`](https://sourcegraph.com/search?q=context:global+repo:github%5C.com/sourcegraph/.*+repo:has.path%28README%29&patternType=keyword)
+- [`repo:has.path(README)`](https://sourcegraph.com/search?q=context:global+repo:github%5C.com/sourcegraph/.*+repo:has.path%28README%29&patternType=keyword)
 
 <Callout type="note">
 	{' '}
-	`repo:contains.path(...)` is an alias for `repo:has.path(..)` and behaves identically.
+	`repo:contains.path(...)` is an alias for `repo:has.path(..)` and behaves
+	identically.
 </Callout>
 
 ### Repo has content
@@ -341,7 +340,7 @@ Search only inside repositories that contain file content matching the regular e
 
 For example,
 
--   [`repo:github\.com/sourcegraph/.*$ repo:has.content(TODO)`](https://sourcegraph.com/search?q=repo:github%5C.com/sourcegraph/.*%24+repo:has.content%28TODO%29&patternType=keyword)
+- [`repo:github\.com/sourcegraph/.*$ repo:has.content(TODO)`](https://sourcegraph.com/search?q=repo:github%5C.com/sourcegraph/.*%24+repo:has.content%28TODO%29&patternType=keyword)
 
 <Callout type="note">
 	`repo:contains.content(...)` is an alias for `repo:has.content(...)` and
@@ -356,7 +355,7 @@ Search only inside repositories that have the given GitHub/GitLab topic.
 
 For example,
 
--   [`repo:has.topic(code-search)`](https://sourcegraph.com/search?q=context%3Aglobal+repo%3Ahas.topic%28code-search%29&patternType=keyword&groupBy=repo)
+- [`repo:has.topic(code-search)`](https://sourcegraph.com/search?q=context%3Aglobal+repo%3Ahas.topic%28code-search%29&patternType=keyword&groupBy=repo)
 
 <Callout type="note">
 	{' '}
@@ -371,12 +370,12 @@ Search only inside repositories that contain a commit after some specified time.
 
 For example,
 
--   [`repo:has.commit.after(1 month ago)`](https://sourcegraph.com/search?q=context:global+repo:.*sourcegraph.*+repo:has.commit.after%281+month+ago%29&patternType=keyword)
+- [`repo:has.commit.after(1 month ago)`](https://sourcegraph.com/search?q=context:global+repo:.*sourcegraph.*+repo:has.commit.after%281+month+ago%29&patternType=keyword)
 
 <Callout type="note">
 	{' '}
-	`repo:contains.commit.after(...)` is an alias for `repo:has.commit.after(...)`
-	and behaves identically.
+	`repo:contains.commit.after(...)` is an alias for
+	`repo:has.commit.after(...)` and behaves identically.
 </Callout>
 
 ### Repo has description
@@ -387,7 +386,7 @@ Search only inside repositories having a description matching the given regular
 
 For example,
 
--   [`repo:has.description(go package)`](https://sourcegraph.com/search?q=context:global+repo:has.description%28go.*package%29+&patternType=keyword)
+- [`repo:has.description(go package)`](https://sourcegraph.com/search?q=context:global+repo:has.description%28go.*package%29+&patternType=keyword)
 
 ## Built-in file predicate
 
@@ -401,12 +400,12 @@ Search only inside files that contain content matching the provided regexp patte
 
 For example,
 
--   [`file:has.content(test)`](https://sourcegraph.com/search?q=context:global+repo:github%5C.com/sourcegraph/.*+file:has.content%28test%29&patternType=keyword)
+- [`file:has.content(test)`](https://sourcegraph.com/search?q=context:global+repo:github%5C.com/sourcegraph/.*+file:has.content%28test%29&patternType=keyword)
 
 <Callout type="note">
 	{' '}
-	`file:contains.content(...)` is an alias for `file:has.content(...)` and behaves
-	identically.
+	`file:contains.content(...)` is an alias for `file:has.content(...)` and
+	behaves identically.
 </Callout>
 
 ### File has owner
@@ -463,28 +462,28 @@ Include commits or diffs that are authored by the user.
 
 Include results having a commit date before the specified time frame. Times are interpreted as UTC by default. Many forms are accepted for the argument, such as:
 
--   `november 1 2019`
--   `1 november 2019`
--   `2019.11.1`
--   `11/1/2019`
--   `01.11.2019`
--   `Thu, 07 Apr 2005 22:13:13 +0200`
--   `2005-04-07`
--   `2005-04-07T22:13:13`
--   `2005-04-07T22:13:13+07:00`
--   `yesterday`
--   `5 days ago`
--   `20 minutes ago`
--   `2 weeks ago`
--   `3:00`
--   `3pm`
--   `1632782809`
--   `1632782809 -0600`
-
-For example,
-
--   [`before:"last thursday"`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph%24+type:diff+author:nick+before:%22last+thursday%22&patternType=regexp)
--   [`before:"november 1 2019"`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph$+type:diff+author:nick+before:%22november+1+2019%22)
+- `november 1 2019`
+- `1 november 2019`
+- `2019.11.1`
+- `11/1/2019`
+- `01.11.2019`
+- `Thu, 07 Apr 2005 22:13:13 +0200`
+- `2005-04-07`
+- `2005-04-07T22:13:13`
+- `2005-04-07T22:13:13+07:00`
+- `yesterday`
+- `5 days ago`
+- `20 minutes ago`
+- `2 weeks ago`
+- `3:00`
+- `3pm`
+- `1632782809`
+- `1632782809 -0600`
+
+For example,
+
+- [`before:"last thursday"`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph%24+type:diff+author:nick+before:%22last+thursday%22&patternType=regexp)
+- [`before:"november 1 2019"`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph$+type:diff+author:nick+before:%22november+1+2019%22)
 
 ### After
 
@@ -492,28 +491,28 @@ For example,
 
 Include results having a commit date after the specified time frame. Times are interpreted as UTC by default. Many forms are accepted for the argument, such as:
 
--   `november 1 2019`
--   `1 november 2019`
--   `2019.11.1`
--   `11/1/2019`
--   `01.11.2019`
--   `Thu, 07 Apr 2005 22:13:13 +0200`
--   `2005-04-07`
--   `2005-04-07T22:13:13`
--   `2005-04-07T22:13:13+07:00`
--   `yesterday`
--   `5 days ago`
--   `20 minutes ago`
--   `2 weeks ago`
--   `3:00`
--   `3pm`
--   `1632782809`
--   `1632782809 -0600`
-
-For example,
-
--   [`after:"6 weeks ago"`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph%24+type:diff+after:%226+weeks+ago%22&patternType=keyword)
--   [`after:"november 1 2019"`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph$+type:diff+author:nick+after:%22november+1+2019%22)
+- `november 1 2019`
+- `1 november 2019`
+- `2019.11.1`
+- `11/1/2019`
+- `01.11.2019`
+- `Thu, 07 Apr 2005 22:13:13 +0200`
+- `2005-04-07`
+- `2005-04-07T22:13:13`
+- `2005-04-07T22:13:13+07:00`
+- `yesterday`
+- `5 days ago`
+- `20 minutes ago`
+- `2 weeks ago`
+- `3:00`
+- `3pm`
+- `1632782809`
+- `1632782809 -0600`
+
+For example,
+
+- [`after:"6 weeks ago"`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph%24+type:diff+after:%226+weeks+ago%22&patternType=keyword)
+- [`after:"november 1 2019"`](https://sourcegraph.com/search?q=repo:sourcegraph/sourcegraph$+type:diff+author:nick+after:%22november+1+2019%22)
 
 ### Message
 
@@ -523,7 +522,7 @@ Include results having a commit message containing the string.
 
 For example,
 
--   [`type:commit message:"testing"`](https://sourcegraph.com/search?q=type:commit+message:%22testing%22+repo:sourcegraph/sourcegraph%24+&patternType=regexp)
+- [`type:commit message:"testing"`](https://sourcegraph.com/search?q=type:commit+message:%22testing%22+repo:sourcegraph/sourcegraph%24+&patternType=regexp)
 
 ## Whitespace
 
diff --git a/docs/code-search/types/search-jobs.mdx b/docs/code-search/types/search-jobs.mdx
index 1efb3cad9..de9d22682 100644
--- a/docs/code-search/types/search-jobs.mdx
+++ b/docs/code-search/types/search-jobs.mdx
@@ -4,24 +4,22 @@
 	Supported on [Enterprise](/pricing/plans/enterprise) plans.
 </TierCallout>
 
-Use Search Jobs to search code at scale for large-scale organizations.
-
-Search Jobs allows you to run search queries across your organization's codebase (all repositories, branches, and revisions) at scale. It enhances the existing Sourcegraph's search capabilities, enabling you to run searches without query timeouts or incomplete results.
+Search Jobs allow you to run search queries across your organization's codebase (all repositories, branches, and revisions) at scale. It enhances the existing Sourcegraph's search capabilities, enabling you to run searches without query timeouts or incomplete results.
 
 With Search Jobs, you can start a search, let it run in the background, and then download the results from the Search Jobs UI when it's done. Site administrators can **enable** or **disable** the Search Jobs feature, making it accessible to all users on the Sourcegraph instance.
 
 ## Using Search Jobs
 
-To use Search Jobs, you need to:
+To use Search Jobs:
 
--   Run a search query from your Sourcegraph instance
--   Click the result menu below the search bar to see if your query is supported by Search Jobs
+- Run a search query from your Sourcegraph instance
+- Click the result menu below the search bar to see if your query is supported by Search Jobs
 
 ![run-query-for-search-jobs](https://storage.googleapis.com/sourcegraph-assets/Docs/search-jobs/search-jobs-create.png)
 
--   If your query is valid, click **Create a search job** to initiate the search job
--   You will be redirected to the "Search Jobs UI" page at `/search-jobs`, where you can view all your created search jobs. If you're a site admin, you can also view search jobs from other users on the instance
--   For each search job, you can download the results by clicking the **Download** button. The results are formatted as JSON lines, see [Search results format](#search-results-format) for more details.
+- If your query is valid, click **Create a search job** to initiate the search job
+- You will be redirected to the "Search Jobs UI" page at `/search-jobs`, where you can view all your created search jobs. If you're a site admin, you can also view search jobs from other users on the instance
+- For each search job, you can download the results by clicking the **Download** button. The results are formatted as JSON lines, see [Search results format](#search-results-format) for more details.
 
 ![view-search-jobs](https://storage.googleapis.com/sourcegraph-assets/Docs/search-jobs/search-jobs-manage-with-frame.png)
 
@@ -38,46 +36,28 @@ The search returned 4 results in 2 files:
 {"type":"content","path":"cmd/embeddings/shared/main.go","repositoryID":399,"repository":"github.com/sourcegraph/sourcegraph","branches":["HEAD"],"commit":"9b47c6430cc3c9cb16695b4fa0a1a277cbbdb327","hunks":null,"chunkMatches":[{"content":"func handlePanic(logger log.Logger, next http.Handler) http.Handler {","contentStart":{"offset":6585,"line":190,"column":0},"ranges":[{"start":{"offset":6590,"line":190,"column":5},"end":{"offset":6601,"line":190,"column":16}}]},{"content":"\thandler = handlePanic(logger, handler)","contentStart":{"offset":2844,"line":81,"column":0},"ranges":[{"start":{"offset":2855,"line":81,"column":11},"end":{"offset":2866,"line":81,"column":22}}]}],"language":"Go"}
 ```
 
-## Configure Search Jobs
-
-Search Jobs requires an object storage to store the results of your search jobs.
-By default, Search Jobs stores results using our bundled `blobstore` service.
-If the `blobstore` service is deployed, and you want to use it to store results from Search Jobs, you don't need to configure anything.
-
-To use a third party managed object storage service, see instructions in [externalizing object storage](/self-hosted/external-services/object-storage#search-job-results).
-
-### Environment Variables
-
-You can configure Search Jobs behavior using the following environment variables on the worker service:
-
-| Environment Variable                     | Default Value | Description                                                                                                                                                                                                                                                                                                                                  |
-| ---------------------------------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `SRC_SEARCH_JOB_WORKER_INTERVAL`         | `1s`          | Controls how frequently the system checks for new search jobs to process. You probably don't need to configure this.                                                                                                                                                                                                                         |
-| `SRC_SEARCH_JOB_MAXIMUM_RUNTIME_PER_JOB` | `5h`          | Sets a maximum time limit for how long a search job can run per repository-revision pair. Note that a search job is run as a collection of many smaller searches, each targeting a single revision of a repository. This ENV targets the maximum runtime of individual searches.                                                             |
-| `SRC_SEARCH_JOB_NUM_HANDLERS`            | `5`           | Adjusts how many searches can run in parallel. A value of 5 (default) means that 5 searches, each targeting a different repository-revision pair, can run in parallel. More handlers put more pressure on the backend, particularly on Searcher and Zoekt. Make sure you have sufficient resources before increasing the number of handlers. |
-
 ## Supported result types
 
 Search jobs supports the following result types:
 
--   `file`
--   `path`
--   `diff`
--   `commit`
+- `file`
+- `path`
+- `diff`
+- `commit`
 
 The following result types are not supported:
 
--   `symbol`
--   `repo`
+- `symbol`
+- `repo`
 
 ## Limitations
 
 The following elements of our query language are not supported:
 
--   file predicates, such as `file:has.content`, `file:has.owner`, `file:has.contributor`, `file:contains.content`
--   catch-all `.*` regexp search
--   Multiple `rev` filters
--   Queries with `index: filter`
+- file predicates, such as `file:has.content`, `file:has.owner`, `file:has.contributor`, `file:contains.content`
+- catch-all `.*` regexp search
+- Multiple `rev` filters
+- Queries with `index: filter`
 
 <Callout type="note">
 	Alternatively, the search bar supports the `count:all` operator which
@@ -87,10 +67,6 @@ The following elements of our query language are not supported:
 	result sets, Search Jobs is the better choice.
 </Callout>
 
-## Disable Search Jobs
-
-To disable Search Jobs, set `DISABLE_SEARCH_JOBS=true` in your frontend and worker services.
-
 ## FAQ
 
 ### How can I run a search job against all branches and all repositories?
diff --git a/docs/code-search/types/structural.mdx b/docs/code-search/types/structural.mdx
index 90f1dc43b..387955629 100644
--- a/docs/code-search/types/structural.mdx
+++ b/docs/code-search/types/structural.mdx
@@ -7,12 +7,14 @@
 
 <Callout type="note">
 	{' '}
-	Changed in version 5.3. Structural search is disabled by default. To enable it,
-	ask your site administrator to set experimentalFeatures.structuralSearch = "enabled"
-	in site configuration. Structural search has performance limitations and is not
-	actively developed. We recommend using regex search or a combination of [Search
-	Jobs](/code-search/types/search-jobs) and custom scripts instead. Please reach out to [support@sourcegraph.com](mailto:support@sourcegraph.com)
-	for guidance on alternative approaches.
+	As of version 5.3, structural search is disabled by default. To enable it,
+	ask your site administrator to set experimentalFeatures.structuralSearch =
+	"enabled" in site configuration. Structural search has performance
+	limitations and is not actively developed. We recommend using regex search
+	or a combination of [Search Jobs](/code-search/types/search-jobs) and custom
+	scripts instead. Please reach out to
+	[support@sourcegraph.com](mailto:support@sourcegraph.com) for guidance on
+	alternative approaches.
 </Callout>
 
 With structural search, you can match richer syntax patterns specifically in code and structured data formats like JSON. It can be awkward or difficult to match code blocks or nested expressions with regular expressions. To meet this challenge we've introduced a new and easier way to search code that operates more closely on a program's parse tree. We use [Comby syntax](https://comby.dev/docs/syntax-reference) for structural matching. Below you'll find examples and notes for this language-aware search functionality.
@@ -62,7 +64,8 @@ The syntax `...` above is an alias for a canonical syntax `:[hole]`, where `hole
 
 <Callout type="note">
 	{' '}
-	To match the string `...` literally, use regular expression patterns like `:[~[.]
+	To match the string `...` literally, use regular expression patterns like
+	`:[~[.]
 	{3}]` or `:[~\.\.\.]`.
 </Callout>
 
@@ -130,7 +133,7 @@ Matches all parts of a JSON document that have a member `"exclude"` where the va
 
 Structural search behaves differently to plain text search in key ways. We are continually improving the functionality of this new feature, so please note the following:
 
--   **Only indexed repos.** Structural search can currently only be performed on _indexed_ repositories. See [configuration](/admin/search) for more details if you host your own Sourcegraph installation. Our service hosted at [sourcegraph.com](https://sourcegraph.com/search) indexes approximately 200,000 of the most popular repositories on GitHub. Other repositories are currently unsupported. To see whether a repository on your instance is indexed, visit `https://<sourcegraph-host>.com/repo-org/repo-name/-/settings/index`.
--   **The `lang` filter is semantically significant.** Adding the `lang` [filter](/code-search/queries) informs the parser about language-specific syntax for comments, strings, and code. This makes structural search more accurate for that language. For example, `fmt.Sprintf(...) lang:go`. If `lang` is omitted, Sourcegraph will attempt a best-effort inference of the language based on matching file extensions or fall back to a generic structural matcher.
--   **Saved searches are not supported.** It is not currently possible to save structural searches.
--   **Matching blocks in indentation-sensitive languages.** It's not currently possible to match blocks of code that are indentation-sensitive. This is a feature planned for future work.
+- **Only indexed repos.** Structural search can currently only be performed on _indexed_ repositories. See [configuration](/admin/search) for more details if you host your own Sourcegraph installation. Our service hosted at [sourcegraph.com](https://sourcegraph.com/search) indexes approximately 200,000 of the most popular repositories on GitHub. Other repositories are currently unsupported. To see whether a repository on your instance is indexed, visit `https://<sourcegraph-host>.com/repo-org/repo-name/-/settings/index`.
+- **The `lang` filter is semantically significant.** Adding the `lang` [filter](/code-search/queries) informs the parser about language-specific syntax for comments, strings, and code. This makes structural search more accurate for that language. For example, `fmt.Sprintf(...) lang:go`. If `lang` is omitted, Sourcegraph will attempt a best-effort inference of the language based on matching file extensions or fall back to a generic structural matcher.
+- **Saved searches are not supported.** It is not currently possible to save structural searches.
+- **Matching blocks in indentation-sensitive languages.** It's not currently possible to match blocks of code that are indentation-sensitive. This is a feature planned for future work.
diff --git a/docs/code-search/types/symbol.mdx b/docs/code-search/types/symbol.mdx
index 18d9cf71f..2d716ed12 100644
--- a/docs/code-search/types/symbol.mdx
+++ b/docs/code-search/types/symbol.mdx
@@ -22,17 +22,17 @@ The extracted `ctags` symbols are also used for the symbol sidebar, which catego
 
 Here is the query path for symbol searches:
 
--   **Zoekt**: if [indexed search](/admin/search#indexed-search) is enabled and the search is for the tip commit of an indexed branch, then Zoekt will service the query and it should respond quickly. Zoekt indexes the default branch (usually `master` or `main`) and can be configured for [multi-branch indexing](/code-search/features#multi-branch-indexing-experimental). The high commit frequency of monorepos reduces the likelihood that Zoekt will be able to respond to symbol searches. Zoekt **eagerly** indexes by listening to repository updates, whereas the searcher service **lazily** indexes the commit being searched.
--   **Searcher service with Rockskip enabled**: if [Rockskip](/code-navigation/rockskip) is enabled, it'll search for symbols stored in Postgres. After initial indexing, queries should be resolved quickly.
--   **Searcher service with an index for the commit**: if the searcher service has already indexed this commit (i.e. someone has visited the commit before) then the query should be resolved quickly. Indexes are deleted in LRU fashion to remain under the configured maximum disk usage which [defaults to 100GB](/code-navigation/search-based-code-navigation#what-configuration-settings-can-i-apply).
--   **Searcher service with an index for a different commit**: if the searcher service has already indexed a **different** commit in the same repository, then it will make a copy of the previous index on disk then run [ctags](https://github.com/universal-ctags/ctags#readme) on the files that changed between the two commits and update the symbols in the new index. This process takes roughly 20 seconds on a monorepo with 40M LOC and 400K files.
--   **Searcher service without any indexes (cold start)**: if the searcher service has never seen this repository before, then it needs to run ctags on all symbols and construct the index from scratch. This process takes roughly 20 minutes on a monorepo with 40M LOC and 400K files.
+- **Zoekt**: if [indexed search](/admin/search#indexed-search) is enabled and the search is for the tip commit of an indexed branch, then Zoekt will service the query with lowest latency. Zoekt indexes the default branch (usually `master` or `main`) and can be configured for [multi-branch indexing](/code-search/features#multi-branch-indexing-experimental). The high commit frequency of monorepos reduces the likelihood that Zoekt will be able to respond to symbol searches. Zoekt **eagerly** indexes by listening to repository updates, whereas the searcher service **lazily** searches the commit.
+- **Searcher service with Rockskip enabled**: if [Rockskip](/code-navigation/rockskip) is enabled, it'll search for symbols stored in Postgres. After initial indexing, queries should be resolved quickly.
+- **Searcher service with an index for the commit**: if the searcher service has already indexed this commit (i.e. someone has visited the commit before) then the query should be resolved quickly. Indexes are deleted in LRU fashion to remain under the configured maximum disk usage which [defaults to 100GB](/code-navigation/search-based-code-navigation#what-configuration-settings-can-i-apply).
+- **Searcher service with an index for a different commit**: if the searcher service has already indexed a **different** commit in the same repository, then it will make a copy of the previous index on disk then run [ctags](https://github.com/universal-ctags/ctags#readme) on the files that changed between the two commits and update the symbols in the new index. This process takes roughly 20 seconds on a monorepo with 40M LOC and 400K files.
+- **Searcher service without any indexes (cold start)**: if the searcher service has never seen this repository before, then it needs to run ctags on all symbols and construct the index from scratch. This process takes roughly 20 minutes on a monorepo with 40M LOC and 400K files.
 
 Once the searcher service has built an index for a commit, here's the query performance:
 
--   Exact matches `^foo$` are optimized to use an index
--   Prefix matches `^foo` are optimized to use an index
--   General regex queries `foo.*bar` are optimized to use an index when using [Rockskip](/code-navigation/rockskip), otherwise the default implementation needs to scan every symbol
--   Path filtering `file:^cmd/` helps narrow the search space
+- Exact matches `^foo$` are optimized to use an index
+- Prefix matches `^foo` are optimized to use an index
+- General regex queries `foo.*bar` are optimized to use an index when using [Rockskip](/code-navigation/rockskip), otherwise the default implementation needs to scan every symbol
+- Path filtering `file:^cmd/` helps narrow the search space
 
 Search-based code navigation uses exact matches `^foo$` and the symbols sidebar uses prefix matches on paths `file:^cmd/` to respond quickly.
diff --git a/docs/code-search/working/saved-searches.mdx b/docs/code-search/working/saved-searches.mdx
index a9dafdbf2..ff5793f20 100644
--- a/docs/code-search/working/saved-searches.mdx
+++ b/docs/code-search/working/saved-searches.mdx
@@ -1,22 +1,22 @@
 # Saved Searches
 
 <p className="subtitle">
-	This page provides docs about how Saved Searches work with Sourcegraph.
+	Saved Searches lets you reuse and share search queries.
 </p>
 
-Saved Searches lets you reuse and share search queries. You can create a saved search for anything, including diffs and commits across all branches of your repositories.
+You can create a saved search for anything, including diffs and commits across all branches of your repositories.
 
-Saved Searches functionality is available to both Free and Enterprise Code Search users. To access or create new Saved Searches in the Sourcegraph web app, click the **Tools > Saved Searches** in the top navigation bar.
+To access or create new Saved Searches in Sourcegraph, click the **More > Saved Searches** in the navigation bar.
 
-![saved-searhces](https://storage.googleapis.com/sourcegraph-assets/Docs/saved-searches-2025.png)
+![saved-searches](https://storage.googleapis.com/sourcegraph-assets/Docs/saved-searches-2025.png)
 
 ## Creating saved searches
 
 To create a new saved search:
 
--   Go to the Saved Searches section and click the **New saved search** button
--   Fill out the description field and enter the search query
--   While writing the query syntax, ensure to include the `patternType:` field
+- Go to the Saved Searches section and click the **New saved search** button
+- Fill out the description field and enter the search query
+- While writing the query syntax, ensure to include the `patternType:` field
 
 A `patternType:` filter is required in the query for all saved searches. `patternType` can be `keyword`, `standard`, `literal`, or `regexp`. You cannot create a saved search without defining the `patternType:` field.
 
diff --git a/docs/code-search/working/search-contexts.mdx b/docs/code-search/working/search-contexts.mdx
index 6e5bbc766..42d9b3315 100644
--- a/docs/code-search/working/search-contexts.mdx
+++ b/docs/code-search/working/search-contexts.mdx
@@ -1,35 +1,24 @@
 # Search Contexts
 
 <p className="subtitle">
-	This page provides docs about Search Contexts in Sourcegraph's Code Search.
+	Search Contexts help you search the code you care about on Sourcegraph.
 </p>
 
-Search Contexts help you search the code you care about on Sourcegraph. A search context represents a set of repositories at specific revisions on a Sourcegraph instance that will be targeted by search queries by default.
+A search context represents a set of repositories at specific revisions on a Sourcegraph instance that will be targeted by search queries by default.
 
 Every search on Sourcegraph uses a search context. Search contexts can be defined with the contexts selector shown in the search input, or entered directly in a search query.
 
 ## Available contexts
 
-**Sourcegraph.com** supports a [set of predefined search contexts](https://sourcegraph.com/contexts?order=spec-asc&visible=17&owner=all) that include:
-
--   The global context, `context:global`, which includes all repositories on Sourcegraph.com.
--   Search contexts for various software communities like [CNCF](https://sourcegraph.com/search?q=context:CNCF), [crates.io](https://sourcegraph.com/search?q=context:crates.io), [JVM](https://sourcegraph.com/search?q=context:JVM), and more.
-
-If no search context is specified, `context:global` is used.
-
-**Private Sourcegraph instances** support custom search contexts:
-
--   Contexts owned by a user, such as `context:@username/context-name`, which can be private to the user or public to all users on the Sourcegraph instance.
--   Contexts at the global level, such as `context:example-context`, which can be private to site admins or public to all users on the Sourcegraph instance.
--   The global context, `context:global`, which includes all repositories on the Sourcegraph instance.
+- Contexts owned by a user, such as `context:@username/context-name`, which can be private to the user or public to all users on the Sourcegraph instance.
+- Contexts at the global level, such as `context:example-context`, which can be private to site admins or public to all users on the Sourcegraph instance.
+- The global context, `context:global`, which includes all repositories on the Sourcegraph instance.
 
 ## Using search contexts
 
-The search contexts selector is shown in the search input. All search queries will target the currently selected search context.
+The search context is selected via the `context:` predicate in the search input. All search queries will target the currently selected search context.
 
-To change the current search context, press the contexts selector. All of your search contexts will be shown in the search contexts dropdown. Select or use the filter to narrow down to a specific search context. Selecting a different context will immediately re-run your current search query using the currently selected search context.
-
-Search contexts can also be used in the search query itself. Type `context:` to begin defining the context as part of the search query. When a context is defined in the search query itself, it overrides the context shown in the context selector.
+Type `context:` to begin defining the context as part of the search query.
 
 You can also search across multiple contexts at once using the `OR` [boolean operator](/code-search/queries#boolean-operators). For example:
 
@@ -37,13 +26,13 @@ You can also search across multiple contexts at once using the `OR` [boolean ope
 
 ## Organizing search contexts
 
-To organize your search contexts better, you can use a specific context as your default and star any number of contexts. This affects what context is selected when loading Sourcegraph and how the list of contexts is sorted.
+To organize your search contexts better, you can use a specific context as your default and star any number of contexts. This affects what context is selected by default, and how the list of contexts is sorted.
 
 ### Default search context
 
 #### For users
 
-Any authenticated user can use a search context as their default. To set a default, go to the search context management page, open the "..." menu for a context, and click on "Use as default". If the user doesn't have a default, `global` will be used.
+Any user can use a search context as their default. To set a default, go to the search context management page, open the "..." menu for a context, and click on "Use as default". If the user doesn't have a default, `global` will be used.
 
 If a user ever loses access to their default search context (eg. the search context is made private), they will see a warning at the top of the search contexts dropdown menu list and `global` will be used. If a user's default search context is deleted, `global` will immediately be set as their default.
 
@@ -55,55 +44,51 @@ Site admins can set a default search context for all users on the Sourcegraph in
 
 An admin can set a default search context via:
 
--   Click the **More** button from the top menu of the Sourcegraph web app
--   Next, go to **Search Contexts**
--   For the existing context list, click on the **...** menu and select **[Site admin only] Set as default for all users**
--   Alternatively, you can create a new context and then set it for all users via the same option
+- Click the **More** button from the menu of the Sourcegraph web app
+- Next, go to **Search Contexts**
+- For the existing context list, click on the **...** menu and select **[Site admin only] Set as default for all users**
+- Alternatively, you can create a new context and then set it for all users via the same option
 
 ![admin-level-default-context](https://storage.googleapis.com/sourcegraph-assets/Docs/admin-default-context.png)
 
 Here are a few considerations:
 
--   If a user already has a personal default search context set, it will not be overridden
--   The admin-set default will apply automatically if a user only uses the global context
--   Individual users can see the instance-wide default and override it with their own default if they choose
+- If a user already has a personal default search context set, it will not be overridden
+- The admin-set default will apply automatically if a user only uses the global context
+- Individual users can see the instance-wide default and override it with their own default if they choose
 
 ### Starred contexts
 
-Any authenticated user can star a search context. To star a context, click on the star icon in the search context management page. This will cause the context to appear near the top of their search contexts list. The `global` context cannot be starred.
+Any user can star a search context. To star a context, click on the star icon in the search context management page. This will cause the context to appear near the top of their search contexts list. The `global` context cannot be starred.
 
 ### Sort order
 
 The order of search contexts in the search results dropdown menu list and in the search context management page is always the following:
 
--   The `global` context first
--   The user's default context, if set
--   All of the user's starred contexts
--   Any remaining contexts available
+- The `global` context first
+- The user's default context, if set
+- All of the user's starred contexts
+- Any remaining contexts available
 
 ## Creating search contexts
 
-When search contexts are [enabled on your private Sourcegraph instance](/code-search/features#search-contexts), you can create your own search contexts.
-
 A search context consists of a name, description, and a set of repositories at one or many revisions.
 
 Contexts can be owned by a user, and can be private to the user or public to all users on the Sourcegraph instance.
 
 Contexts can also be at the global instance level, and can be private to site admins or public to all users on the Sourcegraph instance.
 
-### Creating search contexts from header navigation
-
--   Go to **User menu > Search contexts** in the top navigation bar.
--   Press the **+ Create search context** button.
--   In the **Owner** field, choose whether you will own the context or if it will be global to the Sourcegraph instance. **Note**: At present, the owner of a search context cannot be changed after being created.
--   In the **Context name** field, type in a short, semantic name for the context. The name can be 32 characters max, and contain alphanumeric and `.` `_` `/` `-` characters.
--   Optionally, enter a **Description** for the context. Markdown is supported.
--   Choose the **Visibility** of this context.
-    -   Public contexts are available to everyone on the Sourcegraph instance. Note that private repositories will only be visible to users that have permission to view the repository via the code host.
-    -   Private contexts can only be viewed by their owner, or in the case being globally owned, by site admins.
--   In the **Repositories and revisions** configuration, define which repositories and revisions should be included in the search context. Press **Add repository** to quickly add a template to the configuration.
-    -   Define repositories with valid URLs.
-    -   Define revisions as strings in an array. To specify a default branch, use `"HEAD"`.
+- Go to **More > Search contexts** in the navigation bar.
+- Press the **+ Create search context** button.
+- In the **Owner** field, choose whether you will own the context or if it will be global to the Sourcegraph instance. **Note**: At present, the owner of a search context cannot be changed after being created.
+- In the **Context name** field, type in a short, semantic name for the context. The name can be 32 characters max, and contain alphanumeric and `.` `_` `/` `-` characters.
+- Optionally, enter a **Description** for the context. Markdown is supported.
+- Choose the **Visibility** of this context.
+    - Public contexts are available to everyone on the Sourcegraph instance. Note that private repositories will only be visible to users that have permission to view the repository via the code host.
+    - Private contexts can only be viewed by their owner, or in the case being globally owned, by site admins.
+- In the **Repositories and revisions** configuration, define which repositories and revisions should be included in the search context. Press **Add repository** to quickly add a template to the configuration.
+    - Define repositories with valid URLs.
+    - Define revisions as strings in an array. To specify a default branch, use `"HEAD"`.
 
 For example:
 
@@ -120,12 +105,12 @@ For example:
 ]
 ```
 
--   Press **Test configuration** to validate the repositories and revisions.
--   Press **Create search context** to finish creating your search context.
+- Press **Test configuration** to validate the repositories and revisions.
+- Press **Create search context** to finish creating your search context.
 
 You will be returned to the list of search contexts. Your new search context will appear in the search contexts selector in the search input, and can be [used immediately](#using-search-contexts).
 
-## Query-based search contexts
+## Query-based search contexts (beta)
 
 As of release 3.36, search contexts can be defined with a restricted search query as an alternative to a specific list of repositories and revisions. Allowed filters are: `repo`, `rev`, `file`, `lang`, `case`, `fork`, and `visibility`. `OR` and `AND` expressions are also allowed.
 

From c738589ae5c4f5bdc87b1e7d88729fc04b858d7e Mon Sep 17 00:00:00 2001
From: Erik Seliger <erikseliger@me.com>
Date: Sun, 26 Apr 2026 16:20:02 +0200
Subject: [PATCH 2/2] fixup

---
 docs/admin/code-hosts/index.mdx  | 38 ++++++++++++++++----------------
 docs/admin/permissions/api.mdx   | 10 ++-------
 docs/admin/permissions/index.mdx | 34 +++++++++++++---------------
 3 files changed, 36 insertions(+), 46 deletions(-)

diff --git a/docs/admin/code-hosts/index.mdx b/docs/admin/code-hosts/index.mdx
index d7dc2150c..8571a2e00 100644
--- a/docs/admin/code-hosts/index.mdx
+++ b/docs/admin/code-hosts/index.mdx
@@ -13,13 +13,13 @@ Sourcegraph can sync repositories from code hosts and other similar services. We
 
 Tier 1 code hosts are our highest level of support for code hosts. When leveraging a Tier 1 code host, you can expect:
 
--   Scalable repository syncing - Sourcegraph is able to reliably sync repositories from this code host up to 100k repositories. (SLA TBD)
--   Scalable permissions syncing - Sourcegraph is able to reliably sync permissions from this code host for up to 10k users. (SLA TBD)
--   Authentication - Sourcegraph is able to leverage authentication from this code host (i.e. Login with GitHub).
--   Code Search - A developer can seamlessly search across repositories from this code host. (SLAs TBD)
--   Code Monitors - A developer can create a code monitor to monitor code in this repository.
--   Code Insights - Code Insights reliably works on code sync'd from a tier 1 code host.
--   Batch Changes - A Batch Change can be leveraged to submit code changes back to a tier 1 code host while respecting code host permissions.
+- Scalable repository syncing - Sourcegraph is able to reliably sync repositories from this code host up to 500k repositories.
+- Scalable permissions syncing - Sourcegraph is able to reliably sync permissions from this code host for up to 10k users.
+- Authentication - Sourcegraph is able to leverage authentication from this code host (i.e. Login with GitHub).
+- Code Search - A developer can seamlessly search across repositories from this code host.
+- Code Monitors - A developer can create a code monitor to monitor code in this repository.
+- Code Insights - Code Insights reliably works on code sync'd from a tier 1 code host.
+- Batch Changes - A Batch Change can be leveraged to submit code changes back to a tier 1 code host while respecting code host permissions.
 
 | Code Host                     | Status | Repository Syncing | Permissions Syncing | Authentication | Code Search | Code Monitors | Code Insights | Batch Changes |
 | ----------------------------- | ------ | ------------------ | ------------------- | -------------- | ----------- | ------------- | ------------- | ------------- |
@@ -39,23 +39,23 @@ Tier 1 code hosts are our highest level of support for code hosts. When leveragi
 
 We recognize there are other code hosts including CVS, SVN, and many more. Today, we do not offer native integrations with these code hosts and customers are advised to leverage [Src-srv-git](/admin/code-hosts/non-git) and the [explicit permissions API](/admin/permissions/api) as a way to ingest code and permissions respectively into Sourcegraph.
 
-[Src-srv-git](/admin/code-hosts/non-git) and the [explicit permissions API](/admin/permissions/api) follow the same scale guidance shared above (up to 100k repos and 10k users).
+[Src-srv-git](/admin/code-hosts/non-git) and the [explicit permissions API](/admin/permissions/api) follow the same scale guidance shared above (up to 500k repos and 10k users).
 
 ## Configure a code host connection
 
 **Site admins** can configure Sourcegraph to sync code from the following code hosts:
 
--   [GitHub](/admin/code-hosts/github)
--   [GitLab](/admin/code-hosts/gitlab)
--   [Bitbucket Cloud](/admin/code-hosts/bitbucket-cloud)
--   [Bitbucket Server / Bitbucket Data Center](/admin/code-hosts/bitbucket-server)
--   [Azure DevOps](/admin/code-hosts/azuredevops)
--   [Gerrit](/admin/code-hosts/gerrit)
--   [AWS CodeCommit](/admin/code-hosts/aws-codecommit)
--   [Other Git code hosts (using a Git URL)](/admin/code-hosts/other)
--   [Non-Git code hosts](/admin/code-hosts/non-git)
-    -   [Perforce](/admin/repo/perforce)
-    -   [Plastic SCM](/admin/repo/plasticscm)
+- [GitHub](/admin/code-hosts/github)
+- [GitLab](/admin/code-hosts/gitlab)
+- [Bitbucket Cloud](/admin/code-hosts/bitbucket-cloud)
+- [Bitbucket Server / Bitbucket Data Center](/admin/code-hosts/bitbucket-server)
+- [Azure DevOps](/admin/code-hosts/azuredevops)
+- [Gerrit](/admin/code-hosts/gerrit)
+- [AWS CodeCommit](/admin/code-hosts/aws-codecommit)
+- [Other Git code hosts (using a Git URL)](/admin/code-hosts/other)
+- [Non-Git code hosts](/admin/code-hosts/non-git)
+    - [Perforce](/admin/repo/perforce)
+    - [Plastic SCM](/admin/repo/plasticscm)
 
 ## Rate limits
 
diff --git a/docs/admin/permissions/api.mdx b/docs/admin/permissions/api.mdx
index 45287d839..4f04d1975 100644
--- a/docs/admin/permissions/api.mdx
+++ b/docs/admin/permissions/api.mdx
@@ -14,12 +14,6 @@ E.g. if a code host does not support permission syncing/webhooks or if it would
 It's also a good idea to use explicit permissions API if the source of truth for the codehost permissions is already defined in some external system, e.g. LDAP group membership.
 In that case, it might be less resource intensive to sync the permissions from external source of truth directly via a periodically running routine.
 
-## SLA
-
-Sourcegraph SLA is, that **p95 of write requests to the explicit permissions API will be resolved within 10 seconds**.
-
-Sourcegraph does not provide SLA for how fresh the permissions are, since the data is provided as is to the API.
-
 ## Disadvantages
 
 It is important to note, that when using explicit permissions API, the permissions are written to the database as provided, without further verification that such permissions do exist on the code host side.
@@ -39,8 +33,8 @@ To enable the permissions API, add the following to the [site configuration](/ad
 
 The `bindID` value specifies how to uniquely identify users when setting permissions:
 
--   `username`: You can [set permissions](#setting-repository-permissions-for-users) for users by specifying their Sourcegraph usernames. Using usernames is **preferred**, as usernames are required to be unique for each user.
--   `email`: You can [set permissions](#setting-repository-permissions-for-users) for users by specifying their email addresses (which must be verified primary emails associated with their Sourcegraph user account). This method can lead to unexpected results if there are multiple Sourcegraph user accounts with the same verified email address. Also, the email address is case-sensitive, so it should be exactly the same as set on the sourcegraph UI.
+- `username`: You can [set permissions](#setting-repository-permissions-for-users) for users by specifying their Sourcegraph usernames. Using usernames is **preferred**, as usernames are required to be unique for each user.
+- `email`: You can [set permissions](#setting-repository-permissions-for-users) for users by specifying their email addresses (which must be verified primary emails associated with their Sourcegraph user account). This method can lead to unexpected results if there are multiple Sourcegraph user accounts with the same verified email address. Also, the email address is case-sensitive, so it should be exactly the same as set on the sourcegraph UI.
 
 After you enable the permissions API, you must [set permissions](#setting-repository-permissions-for-users) to allow users to view repositories (site admins bypass all permissions checks and can always view all repositories).
 
diff --git a/docs/admin/permissions/index.mdx b/docs/admin/permissions/index.mdx
index 4ab56387f..d2121e85a 100644
--- a/docs/admin/permissions/index.mdx
+++ b/docs/admin/permissions/index.mdx
@@ -40,7 +40,6 @@ To set up permissions by [syncing them from a code host](/admin/permissions/sync
     - [Bitbucket Cloud](/admin/auth/#bitbucket-cloud)
     - [Bitbucket Server](/admin/auth/#bitbucket-server)
     - [Gerrit](/admin/auth/#gerrit)
-    - Bitbucket Server doesn't require an authentication provider, but has [other prerequisites](/admin/code-hosts/bitbucket-server#prerequisites)
     - Perforce doesn't need a separate authentication provider
     - [Azure DevOps](/admin/code-hosts/azuredevops)
 2. Configure the code host connection to use authorization:
@@ -68,23 +67,23 @@ To know more about each method that we support, please follow the link above.
 
 Support for repository permissions accross different code hosts is different. The following table captures current state of support (ordered alphabetically):
 
-| Code host              | [Permission Syncing](/admin/permissions/syncing) | [Webhooks for Permissions](/admin/permissions/webhooks) | [Explicit API](/admin/permissions/api) | [Scale supported](#supported-scale) |
-| ---------------------- | ------------------------------------------------ | ------------------------------------------------------- | -------------------------------------- | ----------------------------------- |
-| Bitbucket Cloud (Beta) | ✓                                                | ✗                                                       | ✓                                      | 10k users, 100k repositories        |
-| Bitbucket Server       | ✓                                                | ✗                                                       | ✓                                      | 10k users, 100k repositories        |
-| Gerrit (Beta)          | ✓                                                | ✗                                                       | ✓                                      | 10k users, 100k repositories        |
-| GitHub                 | ✓                                                | ✓                                                       | ✓                                      | 40k users, 200k repositories        |
-| GitHub Enterprise      | ✓                                                | ✓                                                       | ✓                                      | 40k users, 200k repositories        |
-| GitLab                 | ✓                                                | ✗                                                       | ✓                                      | 40k users, 200k repositories        |
-| GitLab Self-Managed    | ✓                                                | ✗                                                       | ✓                                      | 40k users, 200k repositories        |
-| Perforce (Beta)        | Yes (with file-level permissions)                | ✓                                                       | ✓                                      | 10k users, 250k repositories        |
-| Azure Devops           | ✓                                                | ✓                                                       | ✓                                      | 10k users, 100k repositories        |
+| Code host           | [Permission Syncing](/admin/permissions/syncing) | [Webhooks for Permissions](/admin/permissions/webhooks) | [Explicit API](/admin/permissions/api) | [Scale supported](#supported-scale) |
+| ------------------- | ------------------------------------------------ | ------------------------------------------------------- | -------------------------------------- | ----------------------------------- |
+| Bitbucket Cloud     | ✓                                                | ✗                                                       | ✓                                      | 10k users, 100k repositories        |
+| Bitbucket Server    | ✓                                                | ✗                                                       | ✓                                      | 10k users, 100k repositories        |
+| Gerrit (Beta)       | ✓                                                | ✗                                                       | ✓                                      | 10k users, 100k repositories        |
+| GitHub              | ✓                                                | ✓                                                       | ✓                                      | 40k users, 200k repositories        |
+| GitHub Enterprise   | ✓                                                | ✓                                                       | ✓                                      | 40k users, 200k repositories        |
+| GitLab              | ✓                                                | ✗                                                       | ✓                                      | 40k users, 200k repositories        |
+| GitLab Self-Managed | ✓                                                | ✗                                                       | ✓                                      | 40k users, 200k repositories        |
+| Perforce (Beta)     | Yes (with file-level permissions)                | ✓                                                       | ✓                                      | 10k users, 250k repositories        |
+| Azure Devops        | ✓                                                | ✓                                                       | ✓                                      | 10k users, 100k repositories        |
 
-All the other code hosts only support [Explicit permissions API](/admin/permissions/api).
+All the other code hosts support the [explicit permissions API](/admin/permissions/api) for deep integrations with external permission management.
 
 ### Supported scale
 
-If not otherwise stated in the table above, all code hosts should support up to 10k users and 100k repositories for permission syncing.
+If not otherwise stated in the table above, all code hosts support up to 10k users and 100k repositories for permission syncing.
 
 These numbers come from testing the supported scale in a testing environment or running on a customer instance.
 
@@ -99,14 +98,11 @@ in Sourcegraph.
 
 - [Permission syncing SLA](/admin/permissions/syncing#sla)
 - [Webhooks SLA](/admin/permissions/webhooks#sla)
-- [Explicit Permissions API SLA](/admin/permissions/api#sla)
 
 ## License requirements
 
-To have permission syncing available, the Sourcegraph instance needs to be configured with
-a license that has `acls` feature enabled. If it is not present, Sourcegraph will not enforce
-repository permissions and each repository will be treated as public - any user that has access
-to Sourcegraph will be able to access it.
+To have permission syncing available, you need a valid Sourcegraph license key. Without a license, Sourcegraph will not enforce
+repository permissions and each repository will be treated as public - any user that has access to Sourcegraph will be able to access it.
 
 ## Site administrators