Change Origin bound certs -> Domain bound certs.

chrome/common/extensions/api/browsingData.json

Index: chrome/common/extensions/api/browsingData.json
diff --git a/chrome/common/extensions/api/browsingData.json b/chrome/common/extensions/api/browsingData.json
index 8848f6e6063cad90679d55bdc4af6905b5d79ff7..7ba52ccc94be068be750f451ce0feeffe6354bd1 100644
--- a/chrome/common/extensions/api/browsingData.json
+++ b/chrome/common/extensions/api/browsingData.json
@@ -79,10 +79,10 @@
                 "optional": true,
                 "description": "Should websites' local storage data be cleared?"
               },
-              "originBoundCertificates": {
+              "serverBoundCertificates": {

[Mihai Parparita -not on Chrome, 2012/03/19 23:15:43]

FYI: This is technically not a backwards-compatible API change (we generally
don't remove methods once they're out of experimental), but since
originBoundCertificates is only on the dev channel, it should be safe to do.

[wtc, 2012/03/19 23:24:10]

Hmm... thanks for pointing this out.

We can consider keeping the old name and just change the
description to say "domain-bound certificates" or
"orgin-bound and domain-bound certificates".

                 "type": "boolean",
                 "optional": true,
-                "description": "Should origin-bound certificates be removed?"
+                "description": "Should server-bound certificates be removed?"
               },
               "pluginData": {
                 "type": "boolean",