fix typo

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: SmilingPixel

README.md

@@ -58,7 +58,7 @@ To install the tool, follow these steps:
   - We use [protoc-gen-openapi](https://github.com/google/gnostic/tree/main/cmd/protoc-gen-openapi) to convert protobuf to openapi.
   - You should annotate the proto file, and you can refer to this [issue](https://github.com/google/gnostic/issues/412).
   - If you use OpenAPI spec, you should ensure that the OpenAPI spec is in the same format as a file generated by the tool (including `operationId`). Note that you must add tag `APIType_HTTP` to all HTTP APIs, as we treat internal service APIs as RPC APIs by default. You can refer to the example at the end of this section.
-3. Optionally, you can provide API dependencies to enhance fuzzing, including system API denpendencies and internal service API denpendencies (a map from service name to single service dependencies). We support parse dependency file generated by RESTler now, you can refer to its [Github Repo](https://github.com/microsoft/restler-fuzzer) for more information.
+3. Optionally, you can provide API dependencies to enhance fuzzing, including system API dependencies and internal service API dependencies (a map from service name to single service dependencies). We support parse dependency file generated by RESTler now, you can refer to its [Github Repo](https://github.com/microsoft/restler-fuzzer) for more information.
 4. Ensure that your service includes a unique trace ID in the headers of each response. You can configure the header key in the settings.
 
 Internal service API Spec example: