Putting the feedback section of the block interstitial to the correct place based on the mocks.

chrome/browser/resources/supervised_user_block_interstitial.css

 /* Copyright 2014 The Chromium Authors. All rights reserved.
  * Use of this source code is governed by a BSD-style license that can be
  * found in the LICENSE file. */
 body {
   background-color: rgb(247, 247, 247);
   font-size: 10pt;
   margin: 150px 60px 0 30px;
 }
 
 #main-frame-blocked {
@@ skipping 15 matching lines @@
   content: -webkit-image-set(
       url(../../app/theme/default_100_percent/cros/logo_avatar_circle_blue_color.png) 1x,
       url(../../app/theme/default_200_percent/cros/logo_avatar_circle_blue_color.png) 2x);
   margin-bottom: 5px;
   margin-right: 15px;
   margin-top: 5px;
   max-width: 45px;
   position: relative;
 }
 
+#feedback {
+  margin-top: 50px;
+}
+
 #feedback-link {
-  font-size: 80%;
-  margin-top: 10px;
+  color: rgb(66, 133, 244);

[Marc Treib, 2016/01/22 00:35:52]

I guess the mocks use a slightly different color from the default link blue? :-/

[atanasova, 2016/01/22 19:32:24]

Yes, it uses the same blue that the button does, the default link color I think
is just blue (it looks different).

 }
 
 #request-access-button {
   background-color: rgb(66, 133, 244);
   color: rgb(255, 255, 255);
   cursor: pointer;
   font-size: 12px;
   font-weight: bold;
   min-width: 88px;
   padding: 10px 15px;
@@ skipping 82 matching lines @@
   }
 
   .hidden-on-mobile {
     display: none;
   }
 
   #main-frame-blocked {
     display: flex;
     flex-flow: column;
   }
+
+  #feedback {
+    margin-top: 35px;
+  }
 }