Skip to content

docs: fix duplicate word in core README#1198

Open
meichuanyi wants to merge 2 commits into
BuilderIO:mainfrom
meichuanyi:docs-fix-readme-duplicate-word
Open

docs: fix duplicate word in core README#1198
meichuanyi wants to merge 2 commits into
BuilderIO:mainfrom
meichuanyi:docs-fix-readme-duplicate-word

Conversation

@meichuanyi

Copy link
Copy Markdown
Contributor

Removes a duplicated word in the core README: in inin.

This is a documentation-only change.

Signed-off-by: meichuanyi <meichuanyi@users.noreply.github.com>
@netlify

This comment has been minimized.

@netlify

This comment has been minimized.

@netlify

This comment has been minimized.

@netlify

This comment has been minimized.

@netlify

This comment has been minimized.

@netlify

This comment has been minimized.

builder-io-integration[bot]

This comment was marked as outdated.

Signed-off-by: meichuanyi <meichuanyi@users.noreply.github.com>

@builder-io-integration builder-io-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Builder reviewed your changes — looks good ✅

Review Details

PR #1198 has been updated with a proper changeset file. The changes include:

  1. Documentation fix (packages/core/README.md, line 196): Removes duplicate word "signs you in in one step" → "signs you in one step"
  2. Changeset file (.changeset/docs-fix-core-readme-duplicate-word.md): Adds a valid patch version bump declaration for @agent-native/core with appropriate description

Both changes are correct, properly formatted, and follow project standards. The changeset format is valid with correct package naming and version bump type. This is a safe, documentation-focused release update.

🧪 Browser testing: Skipped — PR only modifies docs and changeset metadata, no UI or functional impact.

@@ -0,0 +1,5 @@
---

@steve8708 steve8708 Jun 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just realized - we don’t need a patch for a readme update. Let’s remove
this file and should be good to go

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants