From 2f5fc3134a627a58161e59fd698f65a95d9ef796 Mon Sep 17 00:00:00 2001 From: Ash Liu Date: Tue, 30 Jan 2024 14:07:39 +0800 Subject: [PATCH] chore: correct the spelling error (#110) --- LICENSE | 2 +- docs/en/http_protocol_service.md | 2 +- docs/en/serialization.md | 2 +- docs/zh/http_protocol_service.md | 2 +- docs/zh/redis_client_guide.md | 2 +- examples/features/admin/README.md | 2 +- trpc/config/trpc_conf.h | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/LICENSE b/LICENSE index bd2811b6..52ce1092 100644 --- a/LICENSE +++ b/LICENSE @@ -1,7 +1,7 @@ Copyright (C) 2023 THL A29 Limited, a Tencent company. All rights reserved. The below software in this distribution may have been modified by THL A29 Limited ("Tencent Modifications"). All Tencent Modifications are Copyright (C) THL A29 Limited. -tPRC-Cpp is licensed under the Apache License Version 2.0 except for the third-party components listed below. +tRPC-Cpp is licensed under the Apache License Version 2.0 except for the third-party components listed below. Apache License diff --git a/docs/en/http_protocol_service.md b/docs/en/http_protocol_service.md index 81ca8b3d..687fbef5 100644 --- a/docs/en/http_protocol_service.md +++ b/docs/en/http_protocol_service.md @@ -473,7 +473,7 @@ class ApiUserHandler : public ::trpc::http::HttpHandler { #### Register `HttpController` -Using the `TPRC_HTTP_HANDLER` macro, users can easily register `Controller`-like interfaces to the route: +Using the `TRPC_HTTP_HANDLER` macro, users can easily register `Controller`-like interfaces to the route: Note: `Controller` does not inherit the `HttpHandler` class, but only has the same interface signature. diff --git a/docs/en/serialization.md b/docs/en/serialization.md index 871b257d..3c5a5024 100644 --- a/docs/en/serialization.md +++ b/docs/en/serialization.md @@ -8,7 +8,7 @@ the following: * How to use JSON as a message type. * How to use binary data as a message type. -The tPRC framework uses `Protobuf Message` as the request and response message types by default. It also +The tRPC framework uses `Protobuf Message` as the request and response message types by default. It also supports using `trpc` protocol to transmit JSON and binary data messages. In other worlds, JSON and binary data can be used as request and response message types. diff --git a/docs/zh/http_protocol_service.md b/docs/zh/http_protocol_service.md index 187a8373..25048a09 100644 --- a/docs/zh/http_protocol_service.md +++ b/docs/zh/http_protocol_service.md @@ -447,7 +447,7 @@ class ApiUserHandler : public ::trpc::http::HttpHandler { #### 注册 `HttpController` -使用 `TPRC_HTTP_HANDLER` 宏，用户也可以方便地注册类似于 `Controller` 类接口到路由中: +使用 `TRPC_HTTP_HANDLER` 宏，用户也可以方便地注册类似于 `Controller` 类接口到路由中: 提示： Controller 未继承 `HttpHandler` 类，只是接口签名相同。 diff --git a/docs/zh/redis_client_guide.md b/docs/zh/redis_client_guide.md index 42425964..2eccb0df 100644 --- a/docs/zh/redis_client_guide.md +++ b/docs/zh/redis_client_guide.md @@ -9,7 +9,7 @@ ## Redis 协议 -Redis 客户端使用 RESP（Redis的序列化协议）协议与 Redis 服务端进行通信。虽然该协议是专门为 Redis 设计的，但是该协议也可以用于其他客户端-服务器（Client-Server）软件项目。Redis 协议是一种文本协议，客户端和服务器发送的命令或数据以 `\r\n`（CRLF） 结尾。有些开发者会误以为 Redis 协议是以空格分隔的，在使用 tPRC-Cpp 客户端 的时候喜欢自己拼 Redis访 问命令。在不太了解 Redis 协议本身的时候推荐使用 `trpc::redis::cmdgen{}.xxxx` 系列接口生成对应的[command](https://redis.io/commands)，直接把生成的command 传入 proxy 对应接口访问 Redis 服务端。 +Redis 客户端使用 RESP（Redis的序列化协议）协议与 Redis 服务端进行通信。虽然该协议是专门为 Redis 设计的，但是该协议也可以用于其他客户端-服务器（Client-Server）软件项目。Redis 协议是一种文本协议，客户端和服务器发送的命令或数据以 `\r\n`（CRLF） 结尾。有些开发者会误以为 Redis 协议是以空格分隔的，在使用 tRPC-Cpp 客户端 的时候喜欢自己拼 Redis访 问命令。在不太了解 Redis 协议本身的时候推荐使用 `trpc::redis::cmdgen{}.xxxx` 系列接口生成对应的[command](https://redis.io/commands)，直接把生成的command 传入 proxy 对应接口访问 Redis 服务端。 ## 接口形式 diff --git a/examples/features/admin/README.md b/examples/features/admin/README.md index 39d52266..6d3e11a9 100644 --- a/examples/features/admin/README.md +++ b/examples/features/admin/README.md @@ -114,7 +114,7 @@ $ curl http://127.0.0.1:8889/cmds/loglevel # the custom value is 10 before reloading config $ curl http://127.0.0.1:8889/cmds/myhandler1 {"custom_value":10} -# change the "custom:value" of server/trcp_cpp_fiber.yaml to 20, and then reload the config +# change the "custom:value" of server/trpc_cpp_fiber.yaml to 20, and then reload the config $ curl http://127.0.0.1:8889/cmds/reload-config -X POST {"errorcode":0,"message":"reload config ok"} # the custom value is 20 after reloading config diff --git a/trpc/config/trpc_conf.h b/trpc/config/trpc_conf.h index a9976a6c..a4812160 100644 --- a/trpc/config/trpc_conf.h +++ b/trpc/config/trpc_conf.h @@ -44,7 +44,7 @@ void Destroy(); template DefaultConfigPtr Load(const std::string& path, Args&&... opts) { static_assert((std::is_same_v && ...), "Args must be LoadOption objects"); - // Hand it to the tPRC-CPP default loader + // Hand it to the tRPC-CPP default loader std::vector options = {std::forward(opts)...}; return detail::Load(path, std::move(options)); }