Remove bumf from the API keys page

app/templates/views/api-keys.html

@@ -15,25 +15,10 @@
       </h1>
     </div>
     <div class="column-one-third">
-      <a href="{{ url_for('.create_api_key', service_id=current_service.id) }}" class="button align-with-heading">Create new API key</a>
+      <a href="{{ url_for('.create_api_key', service_id=current_service.id) }}" class="button align-with-heading">Create an API key</a>
     </div>
   </div>
 
-  <p>
-    To connect to the API you need to create an API Key.
-  </p>
-  <p>
-    Each service can have multiple API Keys. This allows you to integrate a
-    number of systems, each with its own key. You can also have separate
-    keys for your development and test environments.
-  </p>
-
-  <p>
-    API usage is described in
-    <a href="{{ url_for('.documentation', service_id=current_service.id) }}">the
-    developer documentation</a>.
-  </p>
-
   {% call(item, row_number) list_table(
     keys,
     empty_message="You haven’t created any API keys yet",
@@ -55,6 +40,14 @@
     {% endif %}
   {% endcall %}
 
-  {{ api_key(current_service.id, "Service ID", thing="service ID") }}
+  <div class="bottom-gutter">
+    {{ api_key(current_service.id, "Service ID", thing="service ID") }}
+  </div>
+
+  <p>
+    API usage is described in the
+    <a href="{{ url_for('.documentation', service_id=current_service.id) }}">
+    API documentation</a>.
+  </p>
 
 {% endblock %}

tests/app/main/views/test_api_keys.py

@@ -34,7 +34,7 @@ def test_should_show_empty_api_keys_page(app_,
 
         assert response.status_code == 200
         assert 'You haven’t created any API keys yet' in response.get_data(as_text=True)
-        assert 'Create new API key' in response.get_data(as_text=True)
+        assert 'Create an API key' in response.get_data(as_text=True)
         mock_get_no_api_keys.assert_called_once_with(service_id=service_id)