diff --git a/google/cloud/dataproc_v1/proto/clusters_pb2.py b/google/cloud/dataproc_v1/proto/clusters_pb2.py
index 6d084067..cdfe0bc3 100644
--- a/google/cloud/dataproc_v1/proto/clusters_pb2.py
+++ b/google/cloud/dataproc_v1/proto/clusters_pb2.py
@@ -3353,11 +3353,11 @@
           completed. By default, executables are run on master and all
           worker nodes. You can test a node’s ``role`` metadata to run
           an executable on a master or worker node, as shown below using
-          ``curl`` (you can also use ``wget``):  ::     ROLE=$(curl -H
-          Metadata-Flavor:Google    http://metadata/computeMetadata/v1/i
-          nstance/attributes/dataproc-role)    if [[ "${ROLE}" ==
-          'Master' ]]; then      ... master specific actions ...    else
-          ... worker specific actions ...    fi
+          ``curl`` (you can also use ``wget``):  ROLE=\ :math:`(curl -H
+          Metadata-Flavor:Google  http://metadata/computeMetadata/v1/ins
+          tance/attributes/dataproc-role)  if [[ "`\ {ROLE}" == ‘Master’
+          ]]; then … master specific actions … else … worker specific
+          actions … fi
       encryption_config:
           Optional. Encryption settings for the cluster.
       autoscaling_config:
diff --git a/synth.metadata b/synth.metadata
index 7a7844c7..2b01ec86 100644
--- a/synth.metadata
+++ b/synth.metadata
@@ -4,7 +4,7 @@
       "git": {
         "name": ".",
         "remote": "https://github.com/googleapis/python-dataproc.git",
-        "sha": "40579d265c7c97febcfdec5f79b12ded8c232226"
+        "sha": "2021ceb663c17ccda395fcb7c672a889f7c03526"
       }
     },
     {