-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Refactor and clean up API Markdown docs.
This has been pending for several years. Finally, managed to do with GPT-4 "auto" cleaning language and other consistency issues. 90% GPT4, 10% manual hand-wringing. GPT-4 prompt: ``` - Fix grammar, simplify language, and make language and terms consistent. - Remove superfluous language, avoid unncessary "the"s etc. - Change endpoint description in tables that list endpoints, change to terse imperative language. - Parameter / field description in Parameter tables, don't be imperative or use active sentences. Only describe the parameter passively and tersely. - Remove backticks from all headings and table values. - Format markdown tables. - Standardize "data type" columns values into number, string[], string, JSON. - Remove the "parameter type" column from tables. - Wrap ID parameters in URIs in braces. Eg: /lists/list_id to /lists/{list_id} - Add a markdown line above every API path heading that begins with GET, POST, PUT, DELETE. - Leave the lines starting with `#code-` untouched - Do not add new sections, headings, or any new content. Only edit existing content as described above. - Do not remove any sections or any existing content. ```
- Loading branch information
Showing
10 changed files
with
614 additions
and
519 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.