Incorporate suggestions from code review

Co-authored-by: Patrice Chalin <[email protected]>
Co-authored-by: Juraci Paixão Kröhling <[email protected]>

content/en/docs/security/_index.md

@@ -1,11 +1,9 @@
 ---
 title: Security
 description: How to use OpenTelemetry Collector securely.
-weight: 90
+weight: 10.1
 ---
 
-## Security
-
 When setting up the OpenTelemetry (OTel) Collector, consider implementing
 security best practices in both your hosting infrastructure and your OTel
 Collector configuration.

content/en/docs/security/otel-collector-configuration-best-practices.md

@@ -1,5 +1,6 @@
 ---
 title: OpenTelemetry Collector Configuration Best Practices
+linkTitle: Collector config
 description:
   Follow best practices to securely configure OpenTelemetry Collector.
 weight: 20
@@ -8,8 +9,6 @@ weight: 20
 When setting up configuration for OpenTelemetry (OTel) Collector, consider the
 following practices to better secure your OTel Collector instance.
 
-## Configuration
-
 <!--
 TODO: SHOULD only enable the minimum required components. What are those?
 --->
@@ -33,7 +32,7 @@ today this is not the case.
 ### Safeguards against denial of service attacks
 
 Users should bind receivers' servers to addresses that limit connections to
-authorized users. <!-- Why? -->
+authorized users, so that their Collectors aren't exposed to the public internet or to wider networks than necessary.
 
 For example, if the OTLP receiver OTLP/gRPC server only has local clients, the
 `endpoint` setting SHOULD be bound to `localhost`:

content/en/docs/security/otel-collector-hosting-best-practices.md

@@ -1,5 +1,6 @@
 ---
 title: OpenTelemetry Collector Hosting Best Practices
+linkTitle: Collector hosting
 description: Follow best practices to securely host OpenTelemetry Collector.
 weight: 10
 ---