review: remove explicit config, clarify framework/server config

Author: lmolkova

docs/http/http-spans.md

@@ -316,33 +316,35 @@ HTTP server frameworks and their instrumentations have a limited knowledge about
 
 Certain web frameworks may provide additional information about server. For example CGI specification defines `SERVER_NAME` and `SERVER_PORT` ([RFC 3875][rfc-servername]) variables. HTTP servers usually know server names as they are provided by users in the configuration. See for example, the Apache [`ServerName`][ap-sn] or NGINX [`server_name`][nx-sn] directive.
 
-Still, the original logical service name might not be available to the server HTTP instrumentation and instrumentations MAY provide an option to let users set `server.*` attributes.
+Still, the original logical server name might not be available to the HTTP server instrumentation or be inaccurate.
 
 #### Setting `server.address` and `server.port` attributes
 
+In the context of HTTP server, `server.address` and `server.port` attributes capture logical host and port name and intended, whenever possible, to be the same on the client and server sides.
+
 HTTP server instrumentations SHOULD do the best effort when populating `server.address` and `server.port` attributes and determine them by using the first of the following that applies:
 
-* Explicit user configuration (if supported).
-* Server name and port available through web framework or HTTP server configuration (if known to the instrumentation).
-* The [request target](https://www.rfc-editor.org/rfc/rfc9110.html#target.resource) if it's passed in the absolute form.
 * The original host which may be passed by the reverse proxy in the `host` identifier of the [`Forwarded`][Forwarded] header or in the [`X-Forwarded-Host`][X-Forwarded-Host] header.
+* Server name and port available through web framework or HTTP server properties if they're based on the user configuration. Instrumentations SHOULD NOT use properties that rely on the `Host` header.
+* The [request target][request target] if it's passed in the absolute form.
 * The `Host` header.
 
-As a result, `server.*` attributes capture logical host and port name and intended to be the same on the client and server sides. Application developers MAY capture private host information using applicable [resource attributes](/docs/resource/README.md).
-
 > **Note**: The `Host` header specifies host and port number of the server. The same applies to the `host` identifier of `Forwarded` header, the `X-Forwarded-Host` header, or the authority component in the request target. Instrumentations SHOULD populate both `server.address` and `server.port` attributes by parsing the applicable property.
 
 The `server.address` SHOULD NOT be set if only IP address is available and capturing name would require a reverse DNS lookup.
 
+Application developers MAY overwrite potentially inaccurate values of `server.*` attributes using a [SpanProcessor][SpanProcessor] and MAY capture private host information using applicable [resource attributes](/docs/resource/README.md).
+
 #### Simple client/server example
 
 ![simple-http-server.png](simple-http-server.png)
 
 #### Client/server example with reverse proxy
 
-![reverser-proxy-http-server.png](reverser-proxy-http-server.png)
+![reverse-proxy-http-server.png](reverse-proxy-http-server.png)
 
 [HTTP Host header]: https://tools.ietf.org/html/rfc7230#section-5.4
+[request target]: https://www.rfc-editor.org/rfc/rfc9110.html#target.resource
 [Forwarded]: https://developer.mozilla.org/docs/Web/HTTP/Headers/Forwarded
 [X-Forwarded-Host]: https://developer.mozilla.org/docs/Web/HTTP/Headers/X-Forwarded-Host
 [rfc-servername]: https://tools.ietf.org/html/rfc3875#section-4.1.14
@@ -573,3 +575,4 @@ Span name: `POST /uploads/:document_id`.
 | `error.type`         | `WebSocketDisconnect`                           |
 
 [DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/document-status.md
+[SpanProcessor]: https://github.com/open-telemetry/opentelemetry-specification/tree/v1.26.0/specification/trace/sdk.md#span-processor