docs: Standardize style of component names, especially when used in links (#9251)

* standardize component name style and links pt 1

* component name standardization pt 2

* standardization pt 3

* standardize component names pt 4

* peer review

* fix lnk

* update edit tool actions section

* standardize Agent, agent, agentic

* more style auditing

* missing imports
This commit is contained in:
April I. Murphy
2025-08-01 05:52:18 -07:00
committed by GitHub
parent 8e4577f0a7
commit 15637403ad
81 changed files with 933 additions and 873 deletions

View File

@ -11,8 +11,8 @@ You can use the Langflow API for programmatic interactions with Langflow, such a
* Create and edit flows, including file management for flows.
* Develop applications that use your flows.
* Develop custom components.
* Build Langflow as a dependency of a larger project.
* Contribute to the overall Langflow project.
* Build Langflow as a dependency of a larger application, codebase, or service.
* Contribute to the overall Langflow codebase.
To view and test all available endpoints, you can access the Langflow API's OpenAPI specification at your Langflow deployment's `/docs` endpoint, such as `http://localhost:7860/docs`.
@ -26,7 +26,7 @@ The quickstart demonstrates how to get automatically generated code snippets for
While individual options vary by endpoint, all Langflow API requests share some commonalities, like a URL, method, parameters, and authentication.
As an example of a Langflow API request, the following curl command calls the `/v1/run` endpoint, and it passes a runtime override (`tweaks`) to the flow's Chat Output component:
As an example of a Langflow API request, the following curl command calls the `/v1/run` endpoint, and it passes a runtime override (`tweaks`) to the flow's **Chat Output** component:
```bash
curl --request POST \