Update references to spankind in descriptions (#14616)

Author: jaydeluca

docs/contributing/documenting-instrumentation.md

@@ -86,33 +86,33 @@ At a minimum, every instrumentation metadata file should include a `description`
 
 Some example descriptions:
 
-* This instrumentation enables SERVER spans and metrics for the ActiveJ HTTP server.
+* This instrumentation enables HTTP server spans and HTTP server metrics for the ActiveJ HTTP server.
 * This instrumentation provides context propagation for Akka actors, it does not emit any telemetry
   on its own.
 * The Alibaba Druid instrumentation generates database connection pool metrics for druid data sources.
-* The Apache Dubbo instrumentation provides CLIENT and SERVER spans
-  for Apache Dubbo RPC calls. Each call produces a span named after the Dubbo
-  method, enriched with standard RPC attributes (system, service, method), network
-  attributes, and error details if an exception occurs.
+* The Apache Dubbo instrumentation provides RPC client spans and RPC server spans for Apache Dubbo
+  RPC calls. Each call produces a span named after the Dubbo method, enriched with standard RPC
+  attributes (system, service, method), network attributes, and error details if an exception
+  occurs.
 
 Some notes when writing descriptions:
 
 * You don't always need to explicitly name the instrumentation, and you can start with "This
   instrumentation..."
 * Prefer the convention of using the word "enables" when describing what the instrumentation does,
-  "This instrumentation enables SERVER spans and metrics for the ActiveJ" instead of something like
-  "This instrumentation provides SERVER spans and metrics for the ActiveJ".
+  "This instrumentation **enables** HTTP server spans and HTTP server metrics for the ActiveJ" instead
+  of something like "This instrumentation **provides** HTTP server spans and HTTP server metrics for the ActiveJ".
 * Explicitly state whether the instrumentation generates new telemetry (spans, metrics, logs).
   * If it doesn't generate new telemetry, clearly explain what it's purpose is, for example whether it
     augments or enriches existing telemetry produced by other instrumentations (e.g., by adding
     attributes or ensuring context propagation).
+* When describing the functionality of the instrumentation and the telemetry, specify using
+  [semantic convention categories](https://opentelemetry.io/docs/specs/semconv/) when possible
+  (e.g., "database client spans", "RPC server metrics", "consumer messaging spans").
 * Do not include specific method names, class names, or other low-level implementation details in
   the description unless they are essential to understanding the purpose of the instrumentation.
 * It is not usually necessary to include specific library or framework version numbers in the
   description, unless that context is significant in some way.
-* When an instrumentation generates spans, be specific about the SpanKind (e.g., SERVER, CLIENT,
-  PRODUCER, CONSUMER, INTERNAL).
-  * Capitalize SpanKind values (e.g., SERVER, CLIENT) when used in descriptions.
 
 
 ### Configurations

docs/instrumentation-list.yaml

@@ -1 +1 @@
-description: This instrumentation enables SERVER spans and metrics for the ActiveJ HTTP server.
+description: This instrumentation enables HTTP server spans and HTTP server metrics for the ActiveJ HTTP server.

instrumentation/activej-http-6.0/metadata.yaml

@@ -1 +1,3 @@
-description: This instrumentation enables CLIENT and SERVER spans and metrics for the Akka HTTP client and server.
+description: >
+  This instrumentation enables HTTP client spans and metrics for the Akka HTTP client, and HTTP
+  server spans and metrics for the Akka HTTP server.

instrumentation/akka/akka-http-10.0/metadata.yaml

@@ -1,7 +1,7 @@
-description: The Apache Dubbo instrumentation provides client and server spans for Apache Dubbo
-  RPC calls. Each call produces a span named after the Dubbo method, enriched with standard RPC
-  attributes (system, service, method), network attributes, and error details if an exception
-  occurs.
+description: The Apache Dubbo instrumentation provides RPC client spans and RPC server spans for
+  Apache Dubbo RPC calls. Each call produces a span named after the Dubbo method, enriched with
+  standard RPC attributes (system, service, method), network attributes, and error details if an
+  exception occurs.
 configurations:
   - name: otel.instrumentation.common.peer-service-mapping
     description: Used to specify a mapping from host names or IP addresses to peer services.

instrumentation/apache-dubbo-2.7/metadata.yaml

@@ -1 +1 @@
-description: This instrumentation enables CLIENT spans and metrics for the Apache HttpAsyncClient.
+description: This instrumentation enables HTTP client spans and HTTP client metrics for the Apache HttpAsyncClient.

instrumentation/apache-httpasyncclient-4.1/metadata.yaml

@@ -1 +1 @@
-description: This instrumentation enables CLIENT spans and metrics for versions 2 and 3 of the Apache HttpClient.
+description: This instrumentation enables HTTP client spans and HTTP client metrics for versions 2 and 3 of the Apache HttpClient.

instrumentation/apache-httpclient/apache-httpclient-2.0/metadata.yaml

@@ -1 +1 @@
-description: This instrumentation enables CLIENT spans and metrics for version 4 of the Apache HttpClient.
+description: This instrumentation enables HTTP client spans and HTTP client metrics for version 4 of the Apache HttpClient.

instrumentation/apache-httpclient/apache-httpclient-4.0/metadata.yaml

@@ -1 +1 @@
-description: This instrumentation provides a library integration that enables CLIENT spans and metrics for the Apache HttpClient.
+description: This instrumentation provides a library integration that enables HTTP client spans and HTTP client metrics for the Apache HttpClient.

instrumentation/apache-httpclient/apache-httpclient-4.3/metadata.yaml

@@ -1 +1 @@
-description: This instrumentation enables CLIENT spans and metrics for version 5 of the Apache HttpClient.
+description: This instrumentation enables HTTP client spans and HTTP client metrics for version 5 of the Apache HttpClient.