[editorial] service.md: normalize link to process.md

This PR normalizes the link to process.md, droping the hash to the page title, since that breaks link checking in the OTel website, see open-telemetry/opentelemetry.io#4253 (review).

Author: chalin

docs/attributes-registry/service.md

@@ -40,7 +40,7 @@ However, Collectors can set the `service.instance.id` if they can unambiguously
 for that telemetry. This is typically the case for scraping receivers, as they know the target address and
 port.
 
-**[2]:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md#process), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`.
+**[2]:** MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to `unknown_service:` concatenated with [`process.executable.name`](process.md), e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`.
 
 **[3]:** A string value having a meaning that helps to distinguish a group of services, for example the team name that owns a group of services. `service.name` is expected to be unique within the same namespace. If `service.namespace` is not specified in the Resource then `service.name` is expected to be unique for all services that have no explicit namespace defined (so the empty/unspecified namespace is simply one more valid namespace). Zero-length namespace string is assumed equal to unspecified namespace.
-<!-- endsemconv -->
+<!-- endsemconv -->