Clarify non-permanent error handling in receiver/doc.go (open-telemet…

…ry#7476)

See discussion here open-telemetry#7459 (comment)

It is expected that the receivers should always retry, not just that they may retry.

receiver/doc.go

@@ -32,7 +32,7 @@
 // receiving protocol allows to do that. In case of OTLP/HTTP for example, this means
 // that HTTP 400 response is returned to the sender.
 //
-// If the error is non-Permanent then the nextConsumer.Consume*() call may be retried
+// If the error is non-Permanent then the nextConsumer.Consume*() call should be retried
 // with the same data. This may be done by the receiver itself, however typically it is
 // done by the original sender, after the receiver returns a response to the sender
 // indicating that the Collector is currently overloaded and the request must be