fixing typos

README.md

@@ -260,7 +260,7 @@ Notes:
   public function getCookieAsString(string $name) : ?string;
   ```
     - Returns a named cookie as a string suitable for use as a header value, or
-      or `null` if it does not exist.
+      `null` if it does not exist.
     - Implementations retaining the cookie as a `response_cookie_array`
       MUST convert it to a `response_header_value_string` via the
       [_ResponseCookieHelperService_][] method `composeResponseCookieString()`.
@@ -321,7 +321,7 @@ Notes:
 
 ### _ResponseBodyContent_
 
-The [_ResponseBodyContent_][] inteface affords management and sending of
+The [_ResponseBodyContent_][] interface affords management and sending of
 non-string, resource-intensive, or response-modifying content.
 
 Notes:
@@ -430,7 +430,7 @@ between the two representations, using these two methods:
     - Composes a `response_cookie_array` into a `response_header_value_string`.
     - Implementations MUST NOT encode the cookie name, value, or attributes.
     - Implementations SHOULD use lower case for attribute names but MAY use any
-      other case approved in the relvant RFCs.
+      other case approved in the relevant RFCs.
     - Implementations MUST omit `=<attribute-value>` when the attribute value
       is boolean `true`.
     - Notes:
@@ -548,7 +548,7 @@ difficult to resolve the differences between the projects. Given that the HTTP
 specifications indicate reason phrases are optional, Response-Interop does not
 attempt to resolve those differences.
 
-Implementors desiring a reason phrase are encouraged to add one approriate for
+Implementors desiring a reason phrase are encouraged to add one appropriate for
 the status code, perhaps in their `sendResponse()` logic.
 
 ### Why not put the _ResponseHeadersCollection_ methods directly on the _ResponseStruct_?
@@ -564,7 +564,7 @@ around building a response.
 ### Why does _ResponseHeadersCollection_ allow `string` but not _Stringable_ `$value` types?
 
 None of the researched projects do so. Further, doing so adds complexity to the
-implemetation directives on how to retain such values, as well to the return
+implementation directives on how to retain such values, as well to the return
 typehints on the various getter methods. Avoiding _Stringable_ therefore reduces
 the implementation burden.
 

src/ResponseCookieHelperService.php

@@ -75,7 +75,7 @@ public function parseResponseCookieString(string $setCookieString) : ?array;
      * Implementations MUST NOT encode the cookie name, value, or attributes.
      *
      * Implementations SHOULD use lower case for attribute names but MAY use any
-     * other case approved in the relvant RFCs.
+     * other case approved in the relevant RFCs.
      *
      * Implementations MUST omit `=<attribute-value>` when the attribute value
      * is boolean `true`.

src/ResponseStruct.php

@@ -16,7 +16,7 @@ interface ResponseStruct
     public ResponseStatusLineStruct $statusLine { get; set; }
 
     /**
-     * The headers for the response, including affordances for ookie management.
+     * The headers for the response, including affordances for cookie management.
      */
     public ResponseHeadersCollection $headers { get; set; }