From 2aef60fcfdecdae0cce2897b6213efa62f7dee80 Mon Sep 17 00:00:00 2001
From: Jake Witz <74574233+jwitz@users.noreply.github.com>
Date: Thu, 20 Jul 2023 15:54:33 +0100
Subject: [PATCH] Clarify RegEx requirements (#1981)

This section of the doc made it seem like a URL object is required to use RegEx, but they work fine in just a string array.
---
 packages/website/versioned_docs/version-legacy/config-file.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/packages/website/versioned_docs/version-legacy/config-file.md b/packages/website/versioned_docs/version-legacy/config-file.md
index 7dd0df8eb..932f636ff 100644
--- a/packages/website/versioned_docs/version-legacy/config-file.md
+++ b/packages/website/versioned_docs/version-legacy/config-file.md
@@ -111,9 +111,9 @@ If one `start_urls` item has no `selectors_key` defined, the `default` set will
 
 ### Using regular expressions
 
-The `start_urls` and `stop_urls` options also enable you to use regular expressions to express more complex patterns. This object must at least contain a `url` key targeting a reachable page.
+The `start_urls` and `stop_urls` options also enable you to use regular expressions to express more complex patterns. You can define either an array of regular expressions or an object. The object must at least contain a `url` key targeting a reachable page.
 
-You can also define a `variables` key that will be injected into your specific URL pattern. The following example makes this variable feature clearer:
+If you define your regular expression as an object, you can also define a `variables` key that will be injected into your specific URL pattern. The following example makes this variable feature clearer:
 
 ```json
 {