update clusterfuzz zip instructions as per instructions on
clusterfuzz.com (https://screenshot.googleplex.com/YUcK6pZ9o3pZ94R)

Change-Id: I0534a24b78e2da30e1553e704f841b2f2f83b626
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3906386
Reviewed-by: Adrian Taylor <[email protected]>
Commit-Queue: Hubert Chao <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1053183}
diff --git a/docs/security/clusterfuzz-for-sheriffs.md b/docs/security/clusterfuzz-for-sheriffs.md
index 961ce23..ec0ba53 100644
--- a/docs/security/clusterfuzz-for-sheriffs.md
+++ b/docs/security/clusterfuzz-for-sheriffs.md
@@ -11,7 +11,8 @@
 allows you to upload files to reproduce crashes on various platforms and will
 identify revision ranges when the regression was introduced. If a test case
 requires multiple files, they can be uploaded together in a zip or tar
-archive: the main file needs to contain the words `index`, `crash` or `test`.
+archive: the main file needs to contain the words `run`, `fuzz-` `index.` or
+`crash.`.
 
 Please *do* specify the crbug number when uploading the test case. This will allow
 ClusterFuzz to keep the crbug updated with progress.