Correct the type names used in LoggingMiddleware example README (#467)

### Motivation

Each of our examples includes a covering README. The README for the
logging
middleware example had some comments about the type names that were
inaccurate.

### Modifications

Fix the commentary in the logging middleware example README.

### Result

Fixed the commentary in the logging middleware example README.

### Test Plan

None.

---------

Co-authored-by: Honza Dvorsky <[email protected]>

Author: simonjbeaumont

Examples/logging-middleware-swift-log-example/README.md

@@ -8,12 +8,9 @@ that use `swift-log` to log requests and responses.
 ## Overview
 
 This example extends the [hello-world-urlsession-client-example](../hello-world-urlsession-client-example)
-with a new target, `LoggingMiddleware`, which is then used when creating
-the `Client`.
-
-The `LoggingMiddleware` provides two types:
-- `LoggingClientMiddleware`, which implements the `OpenAPIRuntime.ClientMiddleware` protocol.
-- `LoggingServerMiddleware`, which implements the `OpenAPIRuntime.ServerMiddleware` protocol.
+with a new target, `LoggingMiddleware`, which can be used when creating
+a `Client` or a `Server` because it conforms to both the `ClientMiddleware` and
+`ServerMiddleware` protocols from the `OpenAPIRuntime` library.
 
 Because request and response bodies support streaming and can be arbitrarily
 large, the middleware is configured with a logging policy; one of: