PR fixes

text/0000-opentelemetry-protocol.md

@@ -110,7 +110,7 @@ If the Client does not receive a response to a particular request after a config
 
 - `Success` - telemetry data is successfully processed by the server. If the server receives an empty request (a request that does not carry any telemetry data) the server SHOULD respond with `Success`.
 
-- `FailedNoneRetryable` - processing of telemetry data failed. The client MUST NOT retry sending the same telemetry data. The telemetry data MUST be dropped. This for example can happen when the request contains bad data and cannot be deserialized or otherwise processed by the server. The client SHOULD maintain a counter of such dropped data.
+- `FailedNotRetryable` - processing of telemetry data failed. The client MUST NOT retry sending the same telemetry data. The telemetry data MUST be dropped. This for example can happen when the request contains bad data and cannot be deserialized or otherwise processed by the server. The client SHOULD maintain a counter of such dropped data.
 
 - `FailedRetryable` - processing of telemetry data failed. The client SHOULD record the error and may retry exporting the same data. This can happen when the server is temporarily unable to process the data.
 
@@ -326,7 +326,7 @@ message ExportResponse {
     // sending the same telemetry data. The telemetry data MUST be dropped. 
     // This for example can happen when the request contains bad data and 
     // cannot be deserialized or otherwise processed by the server.
-    FailedNoneRetryable = 1;
+    FailedNotRetryable = 1;
     
     // Processing of telemetry data failed. The client SHOULD record the 
     // error and may retry exporting the same data after some time. This