-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug TiDB Cloud Documentation: Get Started with Data Service #15743
Comments
/assign |
👋 @sgykfjsm, just a quick reminder to make your TiDB Docs Dash contributions by January 12 at 07:59 UTC. Let us know if you have any questions! |
In item 4 of Step 1. Create a Data App,
It would be more clear to clarify this is to be done in the TiDB Cloud console. |
In Step 2. Develop an endpoint
The default |
Yes, agree with you. Thanks for the suggestion. If you're interested, feel free to create a pull request (PR) to update the documentation directly.
|
@qiancai Okay, I will. Let me add some comments more to record what I noticed. |
In Step 2. Develop an endpoint, Write SQL statements, "3. Run SQL statements." This part should be aligned with this page https://docs.pingcap.com/tidbcloud/tidb-cloud-quickstart#step-2-try-ai-powered-chat2query-beta:~:text=Run%20the%20SQL%20queries. |
In Step 4. Deploy the endpoint, item 2,
I cannot see the Deployments tab on the right pane. |
Hi @sgykfjsm, thanks so much for all your valuable comments and PR ❤️. I've reviewed the PR and merged the changes. If you notice any documentation issues in the future, feel free to create an issue or PR in this doc repository. |
This issue is a sub-issue of Debug TiDB Cloud Documentation: Summary Issue · Issue #15480 · pingcap/docs. The purpose of this sub-issue is to verify and debug the Get Started with Data Service document.
You can follow the instructions provided in #15480 to verify and debug the instructions in this document.
Your contribution to testing and verifying the documentation is highly appreciated!
The text was updated successfully, but these errors were encountered: