diff --git a/content/docs/next-release/deployment.md b/content/docs/next-release/deployment.md
index b5eeff96..2a8de706 100644
--- a/content/docs/next-release/deployment.md
+++ b/content/docs/next-release/deployment.md
@@ -85,9 +85,13 @@ docker run \
   --reporter.tchannel.host-port=jaeger-collector.jaeger-infra.svc:14267
 ```
 
+Or add `--reporter.type=grpc` and `--reporter.grpc.host-port=jaeger-collector.jaeger-infra.svc:14250` to use gRPC
+communication with the collector. Then the `tchannel` option can be removed.
+
 In the future we will support different service discovery systems to dynamically load balance
 across several collectors ([issue 213](https://github.com/jaegertracing/jaeger/issues/213)).
 
+
 ## Collectors
 
 The collectors are stateless and thus many instances of **jaeger-collector** can be run in parallel.
@@ -110,6 +114,7 @@ At default settings the collector exposes the following ports:
 Port  | Protocol | Function
 ----- | -------  | ---
 14267 | TChannel | used by **jaeger-agent** to send spans in jaeger.thrift format
+14250 | gRPC     | used by **jaeger-agent** to send spans in model.proto format
 14268 | HTTP     | can accept spans directly from clients in jaeger.thrift format over binary thrift protocol
 9411  | HTTP     | can accept Zipkin spans in JSON or Thrift (disabled by default)
 14269 | HTTP     | Health check at **/**
diff --git a/content/docs/next-release/getting-started.md b/content/docs/next-release/getting-started.md
index 339ffd22..6485e320 100644
--- a/content/docs/next-release/getting-started.md
+++ b/content/docs/next-release/getting-started.md
@@ -45,6 +45,7 @@ Port  | Protocol | Component | Function
 5778  | HTTP     | agent     | serve configs
 16686 | HTTP     | query     | serve frontend
 14268 | HTTP     | collector | accept `jaeger.thrift` directly from clients
+14250 | HTTP     | collector | accept `model.proto`
 9411  | HTTP     | collector | Zipkin compatible endpoint (optional)