| Index: chrome/browser/extensions/api/messaging/incognito_connectability.h
 | 
| diff --git a/chrome/browser/extensions/api/messaging/incognito_connectability.h b/chrome/browser/extensions/api/messaging/incognito_connectability.h
 | 
| index 026ade958ec2f2306ace5d55ba34f34eaf0d3681..9686db2b4f2d723d529323e886149ad1aac23364 100644
 | 
| --- a/chrome/browser/extensions/api/messaging/incognito_connectability.h
 | 
| +++ b/chrome/browser/extensions/api/messaging/incognito_connectability.h
 | 
| @@ -27,11 +27,10 @@ class Extension;
 | 
|  // Tracks the web connectability of domains to extensions in incognito mode.
 | 
|  //
 | 
|  // The most important functionality is prompting the user to allow or disallow
 | 
| -// connections from incognito tabs to extensions or apps. Even if an extension
 | 
| -// hasn't been enabled in incognito mode, it's still useful for web sites to be
 | 
| -// able to send messages to them, with user constent. For apps, it's essential
 | 
| -// we have this functionality because there is no way for them to be enabled in
 | 
| -// incognito.
 | 
| +// connections from incognito tabs to extensions or apps. Users are not prompted
 | 
| +// for extensions which can be enabled in incognito mode. However for apps, it's
 | 
| +// essential we have this functionality because there is no way for them to be
 | 
| +// enabled in incognito.
 | 
|  class IncognitoConnectability : public BrowserContextKeyedAPI {
 | 
|   public:
 | 
|    // While in scope, immediately either accepts or denies the alerts that show
 | 
| 
 |