Fix fput_object typo in changelog

[asuiu]

Summary

• fix README changelog reference to fput_object

Testing

• pre-commit run --files README.md python/README.py.md

---

https://chatgpt.com/codex/tasks/task_e_688bf745e444832f9141f8877398af2b

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Corrected inaccurate method name reference in the release notes for version 1.1.0 to ensure the public API documentation accurately reflects the actual available methods.

Walkthrough

Documentation fix: corrected a typo in the 1.1.0 changelog (method name changed from fput_oject() to fput_object()) and retained the argument rename from destination to file_path. No code or API signatures were modified.

Changes

Cohort / File(s)	Change Summary
Main README and Changelog Fixes README.md	Corrected changelog typo: fput_oject() → fput_object(); retained argument rename destination → file_path; removed trailing whitespace in example.
Python Changelog Correction python/README.py.md	Corrected changelog typo: fput_oject() → fput_object() and clarified the argument rename to file_path.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Review the two README files to confirm only documentation text changed and no code/API signatures were edited.

Poem

✨ Typos fall, the changelog gleams,
A name corrected, precise as beams.
Arguments renamed, the record clear,
No runtime harmed, no tests to fear.
Docs now sharper — onward we steer.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is minimal and lacks required template sections like What & Why, Scope, Risk/Impact, and the self-review checklist specified in the repository guidelines.	Expand the description to follow the repository template: add What & Why section, select appropriate Scope checkbox, complete Risk/Impact assessment, and acknowledge the Author Self-Review Checklist items.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title directly and clearly identifies the main change: fixing a typo in the changelog where fput_object was misspelled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/fix-fput_oject-typo-in-readme-files

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fc3d31e and 4bf39e2.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments (1)

README.md (1)

176-176: Typo squashed. 🚀

The correction from fput_oject() to fput_object() is clean and accurate. This aligns the documentation with the actual API.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b91be22 and fc3d31e.

📒 Files selected for processing (2)

• README.md (2 hunks)
• python/README.py.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

python/README.py.md

[grammar] ~165-~165: Use correct spacing
Context: ...put_object() rename arg: destination -> file_path ##### 1.0.1 - Added ShallowListing to _init...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

README.md

[grammar] ~165-~165: Use correct spacing
Context: ...put_object() rename arg: destination -> file_path ##### 1.0.1 - Added ShallowListing to _init...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

🔇 Additional comments (1)

README.md (1)

79-79: Whitespace turbulence resolved.

The sneaky trailing space after bucket.move_prefix() is gone. Clean docs make for happy engineers.

[coderabbitai]

🧹 Nitpick (assertive)

Typo eliminated, clarity restored – nice.

fput_object() is now spelled correctly. Consider wrapping method and argument names in back-ticks ( IBucket.fput_object(), file_path ) to keep formatting consistent with the rest of the changelog, but otherwise this is ready for liftoff.

🧰 Tools

🪛 LanguageTool

[grammar] ~165-~165: Use correct spacing
Context: ...put_object() rename arg: destination -> file_path ##### 1.0.1 - Added ShallowListing to _init...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

🤖 Prompt for AI Agents

In python/README.py.md at line 165, wrap the method name IBucket.fput_object()
and the argument file_path in back-ticks to maintain consistent formatting with
the rest of the changelog. This means enclosing them in `` to highlight them as
code elements.

[coderabbitai]

🧹 Nitpick (assertive)

Consistent nomenclature achieved.

The corrected bullet (fput_object() + file_path) aligns this README with the codebase. Same minor formatting nit as in the Python README: back-tick the identifiers for perfect consistency.

🧰 Tools

🪛 LanguageTool

[grammar] ~165-~165: Use correct spacing
Context: ...put_object() rename arg: destination -> file_path ##### 1.0.1 - Added ShallowListing to _init...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

🤖 Prompt for AI Agents

In README.md at line 165, the argument name for IBucket.fput_object() was
changed from destination to file_path, but the identifiers are not back-ticked
for consistent formatting. Update the bullet point to enclose both fput_object()
and file_path in back-ticks to match the style used elsewhere in the README and
maintain consistent nomenclature formatting.