@@ -174,7 +174,7 @@ When calling the `AuthenticateProcess` RPC, the Windows service will:
174
174
1 . Use the Windows API ` GetNamedPipeClientProcessId ` to get the pipe client
175
175
process handle.
176
176
1 . Once it has the user process handle, the Windows service can confirm that
177
- it's own exe is identical to the exe of the cleint application connecting to
177
+ it's own exe is identical to the exe of the client application connecting to
178
178
it.
179
179
180
180
### Privacy
@@ -185,10 +185,10 @@ There are no new privacy considerations on Windows.
185
185
186
186
``` protobuf
187
187
// ClientApplicationService is a service the VNet client applications provide to
188
- // the VNet admin process to facilate app queries, certificate issuance,
188
+ // the VNet admin process to facilitate app queries, certificate issuance,
189
189
// metrics, error reporting, and signatures.
190
190
service ClientApplicationService {
191
- // AuthenticateProcess mutually authenticates client applicates to the admin
191
+ // AuthenticateProcess mutually authenticates client applications to the admin
192
192
// service.
193
193
rpc AuthenticateProcess(AuthenticateProcessRequest) returns (AuthenticateProcessResponse);
194
194
// Ping is used by the admin process to regularly poll that the client
@@ -345,7 +345,7 @@ message OnNewConnectionResponse {}
345
345
// OnInvalidLocalPortRequest is a request for OnInvalidLocalPort.
346
346
message OnInvalidLocalPortRequest {
347
347
// app_info identifies the app the request was made for. AppInfo is used
348
- // instaed of AppKey so that the application spec is included, which includes
348
+ // instead of AppKey so that the application spec is included, which includes
349
349
// the TCP port ranges allowed for the app, which are ultimately included in
350
350
// the user error message.
351
351
AppInfo app_info = 1;
0 commit comments