Tied up BlimpNavigationController to NavigationFeature

blimp/client/public/contents/blimp_contents.h

Index: blimp/client/public/contents/blimp_contents.h
diff --git a/blimp/client/public/contents/blimp_contents.h b/blimp/client/public/contents/blimp_contents.h
index 02d7560211c2abf6b8ef196413544039c8a9ad88..be7f3a40ae3da766a8577542f2a4e359d267f37a 100644
--- a/blimp/client/public/contents/blimp_contents.h
+++ b/blimp/client/public/contents/blimp_contents.h
@@ -15,10 +15,12 @@ namespace client {
 class BlimpContentsObserver;
 class BlimpNavigationController;
 
-// BlimpContents is the core class in //blimp/client/core. It renders web pages
-// from an engine in a rectangular area.
-// It enables callers to control the blimp engine through the use of the
-// navigation controller.
+// BlimpContents is the core class in //blimp/client which is responsible for

[Kevin M, 2016/08/03 16:55:16]

This is nice!

You can remove "in //blimp/client" because that detail is well-established by
the file path.

+// rendering web pages in a rectangular area. The interaction with between the
+// client and engine is encapsulated behind this interface through the use of
+// the navigation controller. Each BlimpContents has exactly one
+// BlimpNavigationController which can be used to load URLs, navigate
+// backwards/forward etc. See blimp_navigation_controller.h for more details.
 class BlimpContents : public base::SupportsUserData {
  public:
   // Retrives the navigation controller that controls all navigation related