@@ -101,7 +101,7 @@ additional filters are applied.
101101
102102If the operation has completed successfully, instrumentations SHOULD NOT set ` error.type ` .
103103
104- If a specific domain defines its own set of error identifiers (such as HTTP or gRPC status codes),
104+ If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes),
105105it's RECOMMENDED to:
106106
107107- Use a domain-specific attribute
@@ -213,7 +213,7 @@ additional filters are applied.
213213
214214If the operation has completed successfully, instrumentations SHOULD NOT set ` error.type ` .
215215
216- If a specific domain defines its own set of error identifiers (such as HTTP or gRPC status codes),
216+ If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes),
217217it's RECOMMENDED to:
218218
219219- Use a domain-specific attribute
@@ -310,7 +310,7 @@ additional filters are applied.
310310
311311If the operation has completed successfully, instrumentations SHOULD NOT set ` error.type ` .
312312
313- If a specific domain defines its own set of error identifiers (such as HTTP or gRPC status codes),
313+ If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes),
314314it's RECOMMENDED to:
315315
316316- Use a domain-specific attribute
@@ -414,7 +414,7 @@ additional filters are applied.
414414
415415If the operation has completed successfully, instrumentations SHOULD NOT set ` error.type ` .
416416
417- If a specific domain defines its own set of error identifiers (such as HTTP or gRPC status codes),
417+ If a specific domain defines its own set of error identifiers (such as HTTP or RPC status codes),
418418it's RECOMMENDED to:
419419
420420- Use a domain-specific attribute
0 commit comments