Skip to content

Commit 85f92f6

Browse files
glbrnttgjcairo
andauthored
Apply suggestions from code review
Co-authored-by: Gus Cairo <[email protected]>
1 parent 2151268 commit 85f92f6

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

Sources/GRPCCore/Call/ConditionalInterceptor.swift

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ extension ConditionalInterceptor where Interceptor == any ClientInterceptor {
101101
extension ConditionalInterceptor where Interceptor == any ServerInterceptor {
102102
/// Create an operation, specifying which ``ServerInterceptor`` to apply and to which ``Subject``.
103103
/// - Parameters:
104-
/// - interceptor: The ``ServerInterceptor`` to register with the client.
104+
/// - interceptor: The ``ServerInterceptor`` to register with the server.
105105
/// - subject: The ``Subject`` to which the `interceptor` applies.
106106
public static func apply(
107107
_ interceptor: any ServerInterceptor,

Sources/GRPCCore/Call/Server/ServerInterceptor.swift

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@
2121
/// been returned from a service. They are typically used for cross-cutting concerns like filtering
2222
/// requests, validating messages, logging additional data, and tracing.
2323
///
24-
/// Interceptors can be registered with the server either directly or via ``ConditionalInterceptor``s.
24+
/// Interceptors can be registered with the server either directly or via ``ConditionalInterceptor``s.
2525
/// You may register them for all services registered with a server, for RPCs directed to specific services, or
2626
/// for RPCs directed to specific methods. If you need to modify the behavior of an interceptor on a
2727
/// per-RPC basis in more detail, then you can use the ``ServerContext/descriptor`` to determine

0 commit comments

Comments
 (0)