Skip to content

Fix some typos in comment #763

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wenchenglu merged 1 commit into from
Jan 25, 2019
Merged

Fix some typos in comment #763

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions mixer/adapter/model/v1beta1/infrastructure_backend.pb.go
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions mixer/adapter/model/v1beta1/infrastructure_backend.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
//
Expand Down Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions mixer/adapter/model/v1beta1/istio.mixer.adapter.model.v1beta1.pb.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>

Expand Down Expand Up @@ -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
Expand Down