aboutsummaryrefslogtreecommitdiffhomepage
path: root/TROUBLESHOOTING.md
diff options
context:
space:
mode:
authorGravatar Jan Tattermusch <jtattermusch@users.noreply.github.com>2018-07-06 14:46:40 +0200
committerGravatar GitHub <noreply@github.com>2018-07-06 14:46:40 +0200
commita811fd63d186e02a364ccf6fcfc7a3249c1a1277 (patch)
tree1a511c185e69739d538b771aecc0880432b72dc6 /TROUBLESHOOTING.md
parentc81a4656de1112db06bfd3fff058aee950096691 (diff)
Update TROUBLESHOOTING.md
Diffstat (limited to 'TROUBLESHOOTING.md')
-rw-r--r--TROUBLESHOOTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/TROUBLESHOOTING.md b/TROUBLESHOOTING.md
index e2fd643ef4..aab23f49da 100644
--- a/TROUBLESHOOTING.md
+++ b/TROUBLESHOOTING.md
@@ -2,7 +2,7 @@
This guide is for troubleshooting gRPC implementations based on C core library (sources for most of them are living in the `grpc/grpc` repository).
-## Enabling extra logging and traces
+## Enabling extra logging and tracing
Extra logging can be very useful for diagnosing problems. All gRPC implementations based on C core library support
the `GRPC_VERBOSITY` and `GRPC_TRACE` environment variables that can be used to increase the amount of information