diff --git a/grpc-auth-support.md b/grpc-auth-support.md
index aff952a0503a555445a13c2f1e49675e53fee27c..336e0ca443a8fc1c908ffbb356aa2060580589be 100644
--- a/grpc-auth-support.md
+++ b/grpc-auth-support.md
@@ -31,7 +31,7 @@ Tokens to each request being made on the channel.
 This is the simplest authentication scenario, where a client just wants to
 authenticate the server and encrypt all data.
 
-```
+```cpp
 SslCredentialsOptions ssl_opts;  // Options to override SSL params, empty by default
 // Create the credentials object by providing service account key in constructor
 std::unique_ptr<Credentials> creds = CredentialsFactory::SslCredentials(ssl_opts);
@@ -52,7 +52,7 @@ passed to the factory method.
 
 gRPC applications can use a simple API to create a credential that works in various deployment scenarios.
 
-```
+```cpp
 std::unique_ptr<Credentials> creds = CredentialsFactory::GoogleDefaultCredentials();
 // Create a channel, stub and make RPC calls (same as in the previous example)
 std::shared_ptr<ChannelInterface> channel = CreateChannel(server_name, creds, channel_args);
@@ -121,7 +121,7 @@ stub = Helloworld::Greeter::Stub.new('localhost:50051')
 ...
 
 # Authenticating with Google
-require 'googleauth'  # from [googleauth](http://www.rubydoc.info/gems/googleauth/0.1.0)
+require 'googleauth'  # from http://www.rubydoc.info/gems/googleauth/0.1.0
 ...
 creds = GRPC::Core::Credentials.new(load_certs)  # load_certs typically loads a CA roots file
 scope = 'https://www.googleapis.com/auth/grpc-testing'