Skip to content

docs: fix typos in README vision intro graphic - #3154

Open
Solaris-star wants to merge 2 commits into
eosphoros-ai:mainfrom
Solaris-star:fix/3072-docs-vision-typos
Open

docs: fix typos in README vision intro graphic#3154
Solaris-star wants to merge 2 commits into
eosphoros-ai:mainfrom
Solaris-star:fix/3072-docs-vision-typos

Conversation

@Solaris-star

Copy link
Copy Markdown

Description

Fix English typos in the README intro vision graphic assets/dbgpt_vision.png reported in #3072.

Corrected misspellings include:

  • quarying → querying
  • Intenrate → Integrate
  • Retrievel → Retrieval
  • BAG → RAG
  • desomposes → decomposes
  • crchestrates → orchestrates
  • fierative → iterative
  • quories → queries
  • decisiop → decision
  • treceability → traceability
  • teliable → reliable
  • date security → data security

How Has This Been Tested?

  • OCR before/after on assets/dbgpt_vision.png (tesseract eng)
  • Confirmed old misspellings are gone and corrected words appear in OCR output

Snapshots:

N/A (binary asset update of existing README graphic)

Checklist:

  • My code follows the style guidelines of this project
  • I have already rebased the commits and make the commit message conform to the project standard.
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • Any dependent changes have been merged and published in downstream modules

Correct misspellings in assets/dbgpt_vision.png (e.g. querying,
Integrate, Retrieval, decomposes, orchestrates, iterative, queries,
decision, traceability, reliable, RAG, data security).

Fixes eosphoros-ai#3072
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • assets/dbgpt_vision.png is excluded by !**/*.png

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 425db553-3ef0-491a-aa0c-44023b7c885c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Jul 21, 2026
@chenliang15405

Copy link
Copy Markdown
Collaborator

Thanks for your fix, It appears that there are obvious signs of photo editing, and the style is not very compatible. It is better to regenerate it.

Fully redraw the intro architecture image so typo fixes are baked into
a clean diagram (no patched/photo-edited text regions).

Fixes remaining review feedback on eosphoros-ai#3154 / eosphoros-ai#3072.
@Solaris-star

Copy link
Copy Markdown
Author

Thanks @chenliang15405 for the feedback.

I fully regenerated assets/dbgpt_vision.png as a clean architecture graphic (not a photo-edit patch), keeping the same overall layout/sections while baking in the corrected spellings (querying / Integrate / Retrieval / RAG / decomposes / orchestrates / iterative / queries / decision / traceability / reliable / data security).

Please take another look when convenient.

@chenliang15405

Copy link
Copy Markdown
Collaborator

Thanks @chenliang15405 for the feedback.

I fully regenerated assets/dbgpt_vision.png as a clean architecture graphic (not a photo-edit patch), keeping the same overall layout/sections while baking in the corrected spellings (querying / Integrate / Retrieval / RAG / decomposes / orchestrates / iterative / queries / decision / traceability / reliable / data security).

Please take another look when convenient.

Is it possible to maintain consistency in style and format?

@Solaris-star

Copy link
Copy Markdown
Author

Thanks for the follow-up! The regenerated image uses the same overall layout, color scheme, and section structure as the original — just with corrected spellings baked in. If there's a specific style or format inconsistency you're seeing, could you point it out? Happy to adjust to match the repo's visual conventions exactly.

@chenliang15405

Copy link
Copy Markdown
Collaborator

Thanks for the follow-up! The regenerated image uses the same overall layout, color scheme, and section structure as the original — just with corrected spellings baked in. If there's a specific style or format inconsistency you're seeing, could you point it out? Happy to adjust to match the repo's visual conventions exactly.

seeing

The most recently submitted item appears to be another image, rather than one with the same style and format, correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants