[Extensions] Fix the link to _behavior_features.json from _features.md

chrome/common/extensions/api/_features.md

 # Extension Features Files
 
 [TOC]
 
 ## Summary
 
 The Extension features files specify the different requirements for extension
 feature availability.
 
 An **extension feature** can be any component of extension capabilities. Most
 notably, this includes extension APIs, but there are also more structural or
 behavioral features, such as web accessible resources or event pages.
 
 ## Files
 
 There are four different feature files used:
 * [\_api\_features](https://chromium.googlesource.com/chromium/src/+/master/chrome/common/extensions/api/_api_features.json):
 Specifies the requirements for API availability. If an extension doesn't satisfy
 the requirements, the API will not be accessible in the extension's code.
 * [\_permission\_features](https://chromium.googlesource.com/chromium/src/+/master/chrome/common/extensions/api/_permission_features.json):
 Specifies the requirements for permission availability. If an extension doesn't
 satisfy the requirements, the permission will not be granted and the extension
 will have an install warning.
 * [\_manifest\_features](https://chromium.googlesource.com/chromium/src/+/master/chrome/common/extensions/api/_manifest_features.json):
 Specifies the requirements for manifest entry availability. If an extension
 doesn't satisfy the requirements, the extension will fail to load with an error.
-* [\_behavior\_features](https://chromium.googlesource.com/chromium/src/+/master/chrome/common/extensions/api/_behavior_features.json):
+* [\_behavior\_features](https://chromium.googlesource.com/chromium/src/+/master/extensions/common/api/_behavior_features.json):
 Specifies the requirements for miscellaneous extension behaviors. This should
 typically not be used.
 
 Note that these files may be present under chrome/common/extensions/api, as well
 as under extensions/common/api and extensions/shell/common/api.
 
 ## Grammar
 
 The feature files are written in JSON. Each file contains a single JSON object
 with properties for each feature.
@@ skipping 411 matching lines @@
 at runtime, this has the added benefit of allowing us to validate at compile
 time rather than needing a unittest (or allowing incorrect features).
 
 In theory, invalid features should result in a compilation failure; in practice,
 the compiler is probably missing some cases.
 
 ## Still to come
 
 TODO(devlin): Add documentation for extension types. Probably also more on
 requirements for individual features.