chore: update wording of new param (#2185)

firestore-bigquery-export/README.md

@@ -126,7 +126,7 @@ To install an extension, your project must be on the [Blaze (pay as you go) plan
 
 * Collection path: What is the path of the collection that you would like to export? You may use `{wildcard}` notation to match a subcollection of all documents in a collection (for example: `chatrooms/{chatid}/posts`). Parent Firestore Document IDs from `{wildcards}`  can be returned in `path_params` as a JSON formatted string.
 
-* Enable logging failed exports: If enabled, the extension will exports that failed to enqueue to the Firebase console, to prevent data loss.
+* Enable logging failed exports: If enabled, the extension will log event exports that failed to enqueue to Cloud Logging, to mitigate data loss.
 
 * Enable Wildcard Column field with Parent Firestore Document IDs: If enabled, creates a column containing a JSON object of all wildcard ids from a documents path.
 

firestore-bigquery-export/extension.yaml

@@ -209,8 +209,8 @@ params:
   - param: LOG_FAILED_EXPORTS
     label: Enable logging failed exports
     description: >-
-      If enabled, the extension will export what failed to enqueue to the
-      Firebase console, to mitigate data loss.
+      If enabled, the extension will log event exports that failed to enqueue to
+      Cloud Logging, to mitigate data loss.
     type: select
     options:
       - label: Yes