diff --git a/mixer/adapter/model/v1beta1/infrastructure_backend.pb.go b/mixer/adapter/model/v1beta1/infrastructure_backend.pb.go
index 2ac30899c0..1e0dadb837 100644
--- a/mixer/adapter/model/v1beta1/infrastructure_backend.pb.go
+++ b/mixer/adapter/model/v1beta1/infrastructure_backend.pb.go
@@ -470,7 +470,7 @@ type InfrastructureBackendClient interface {
 	//
 	// Backend is allowed to return the same session id if given the same configuration block.
 	// This would happen when multiple instances of Mixer in a deployment all create sessions with the same configuration.
-	// Note that given individial instances of Mixer can call `CloseSession`, reusing `session_id` by the backend
+	// Note that given individual instances of Mixer can call `CloseSession`, reusing `session_id` by the backend
 	// assumes that the backend is doing reference counting.
 	//
 	// If the backend couldn't create a session for a specific handler configuration and
@@ -538,7 +538,7 @@ type InfrastructureBackendServer interface {
 	//
 	// Backend is allowed to return the same session id if given the same configuration block.
 	// This would happen when multiple instances of Mixer in a deployment all create sessions with the same configuration.
-	// Note that given individial instances of Mixer can call `CloseSession`, reusing `session_id` by the backend
+	// Note that given individual instances of Mixer can call `CloseSession`, reusing `session_id` by the backend
 	// assumes that the backend is doing reference counting.
 	//
 	// If the backend couldn't create a session for a specific handler configuration and
diff --git a/mixer/adapter/model/v1beta1/infrastructure_backend.proto b/mixer/adapter/model/v1beta1/infrastructure_backend.proto
index 0522d09c27..71839d26b9 100644
--- a/mixer/adapter/model/v1beta1/infrastructure_backend.proto
+++ b/mixer/adapter/model/v1beta1/infrastructure_backend.proto
@@ -31,7 +31,7 @@ import "google/rpc/status.proto";
 // out of process adapter.
 //
 // `InfrastructureBackend` allows Mixer and the backends to have a session based model. In a session based model, Mixer passes
-// the relevant configuration state to the backend only once and estabilshes a session using a session identifier.
+// the relevant configuration state to the backend only once and establishes a session using a session identifier.
 // All future communications between Mixer and the backend uses the session identifier which refers to the previously
 // passed in configuration data.
 //
@@ -59,7 +59,7 @@ service InfrastructureBackend {
     //
     // Backend is allowed to return the same session id if given the same configuration block.
     // This would happen when multiple instances of Mixer in a deployment all create sessions with the same configuration.
-    // Note that given individial instances of Mixer can call `CloseSession`, reusing `session_id` by the backend
+    // Note that given individual instances of Mixer can call `CloseSession`, reusing `session_id` by the backend
     // assumes that the backend is doing reference counting.
     //
     // If the backend couldn't create a session for a specific handler configuration and
diff --git a/mixer/adapter/model/v1beta1/istio.mixer.adapter.model.v1beta1.pb.html b/mixer/adapter/model/v1beta1/istio.mixer.adapter.model.v1beta1.pb.html
index d77945c0cc..8ab59eb324 100644
--- a/mixer/adapter/model/v1beta1/istio.mixer.adapter.model.v1beta1.pb.html
+++ b/mixer/adapter/model/v1beta1/istio.mixer.adapter.model.v1beta1.pb.html
@@ -15,7 +15,7 @@ <h3 id="InfrastructureBackend">InfrastructureBackend</h3>
 out of process adapter.</p>
 
 <p><code>InfrastructureBackend</code> allows Mixer and the backends to have a session based model. In a session based model, Mixer passes
-the relevant configuration state to the backend only once and estabilshes a session using a session identifier.
+the relevant configuration state to the backend only once and establishes a session using a session identifier.
 All future communications between Mixer and the backend uses the session identifier which refers to the previously
 passed in configuration data.</p>
 
@@ -46,7 +46,7 @@ <h3 id="InfrastructureBackend">InfrastructureBackend</h3>
 
 <p>Backend is allowed to return the same session id if given the same configuration block.
 This would happen when multiple instances of Mixer in a deployment all create sessions with the same configuration.
-Note that given individial instances of Mixer can call <code>CloseSession</code>, reusing <code>session_id</code> by the backend
+Note that given individual instances of Mixer can call <code>CloseSession</code>, reusing <code>session_id</code> by the backend
 assumes that the backend is doing reference counting.</p>
 
 <p>If the backend couldn&rsquo;t create a session for a specific handler configuration and