remove single line para under h2s

security/shared-responsibility.html.markerb

@@ -14,8 +14,6 @@ There's also a lot of software involved, but the important ones are flyd which m
 
 ## Fly.io's responsibilities
 
-The following areas are managed by Fly.io.
-
 ### Hardening and protection of infrastructure systems
 
 Fly.io is solely responsible for the security of our infrastructure systems, including workers, edges and gateways. This includes managing access, applying security patches to the operating system, other 3rd-party software (e.g. firecracker), and mitigating hardware vulnerabilities where appropriate. Fly.io monitors these systems in both an operational and security capacity.
@@ -39,8 +37,6 @@ Fly.io was built with security front and centre. Visit our [Security](https://fl
 
 ## Your responsibilities
 
-The following areas are managed by you.
-
 ### Everything within your Docker image and therefore Fly Machines
 
 We generally consider our demarcation point the virtualization boundary between our worker (virtualization host) and the Fly Machine (virtualization guest). The Fly Machine is constructed from your instructions, and therefore its contents are your responsibility. This includes: the system userspace and libraries, your application code, your application environment, and the services you run.