Fix incorrect API terminology in client API documentation #1044
+36
−36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Section 0.1 "统一路径格式" (Unified Path Format) of the client API documentation incorrectly used "运维API" (Operations API) terminology instead of "客户端API" (Client API).
Changes
src/content/docs/{latest,next,v3.0}/zh-cn/manual/user/open-api.mdsrc/content/docs/{latest,next,v3.0}/en/manual/user/open-api.md$nacos.server.contextPath,module,subPath), and context statementsNote: English documentation files contain untranslated Chinese text awaiting future translation work. Terminology corrected for consistency.
Original prompt
This pull request was created from Copilot chat.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.