diff --git a/src/content/documentation/develop/extensions-and-the-add-on-id.md b/src/content/documentation/develop/extensions-and-the-add-on-id.md
index a8b451e83..8b9529026 100644
--- a/src/content/documentation/develop/extensions-and-the-add-on-id.md
+++ b/src/content/documentation/develop/extensions-and-the-add-on-id.md
@@ -108,7 +108,7 @@ See [`browser_specific_settings` in manifest.json](https://developer.mozilla.org
 
 ## Working without an ID in Manifiest V2
 
-An add-on ID is optional for Manifest V2 extensions. If you don't set it, you can generally develop, debug, publish, and update your extension without ever having to deal with an ID. One advantage of this is that Google Chrome does not recognize the `browser_specific_settings` key and shows a warning if you include it.
+An add-on ID is optional for Manifest V2 extensions. If you don't set it, you can generally develop, debug, publish, and update your extension without ever having to deal with an ID. However, if you do add the `browser_specific_settings` manifest key (to add an ID), Google Chrome ignores it, and Apple Safari ignores Firefox's `gecko` and `gecko_android` sub-keys.
 
 However, there are some implications of not setting an add-on ID that are described in this section.