merge with master

Author: Adriano Santos

grpc_server/guides/advanced/custom_codecs.md

@@ -300,5 +300,4 @@ If you need custom encoding for HTTP endpoints, consider:
 - **Custom codecs are NOT supported for HTTP transcoding** - only `GRPC.Codec.JSON` is used
 
 For more examples, see the test suite:
-- `test/grpc/integration/custom_codec_test.exs`
-- `test/grpc/codec/proto_test.exs`
+- `test/grpc/codec/proto_test.exs`

grpc_server/guides/advanced/transcoding.livemd

@@ -212,6 +212,6 @@ $ curl -XPOST -H 'Content-type: application/json' -d '{"name": "test", "from": "
 
 >__Note__: gRPC Transcode HttpRule https://docs.cloud.google.com/endpoints/docs/grpc-service-config/reference/rpc/google.api#google.api.HttpRule
 
-> __Warning__: HTTP transcoding **always** uses `GRPC.Codec.JSON` for encoding and decoding, regardless of any custom codecs configured in your server. This is by design, as HTTP transcoding follows the standard HTTP/JSON to gRPC mapping specification. If you need custom serialization formats, use standard gRPC (HTTP/2) instead. For more details, see the [Custom Codecs](custom_codecs.md) guide.                     
+> __Warning__: HTTP transcoding **always** uses `GRPC.Codec.JSON` for encoding and decoding, regardless of any custom codecs configured in your server. This is by design, as HTTP transcoding follows the standard HTTP/JSON to gRPC mapping specification. If you need custom serialization formats, use standard gRPC (HTTP/2) instead. For more details, see the [Custom Codecs](custom_codecs.md) guide.              
 
 ---