Skip to content

docs(source-paypal-transaction): fix spelling, grammar, and changelog date#74076

Draft
devin-ai-integration[bot] wants to merge 1 commit intomasterfrom
devin/1772154665-paypal-transaction-docs-update
Draft

docs(source-paypal-transaction): fix spelling, grammar, and changelog date#74076
devin-ai-integration[bot] wants to merge 1 commit intomasterfrom
devin/1772154665-paypal-transaction-docs-update

Conversation

@devin-ai-integration
Copy link
Contributor

What

Improves the source-paypal-transaction connector documentation by fixing spelling/grammar errors, correcting the changelog date for v2.6.26, and fixing a technical inaccuracy. Triggered by review of commit 16eda09 (#74027).

How

Single-file edit to docs/integrations/sources/paypal-transaction.md:

  • Spelling/grammar: Fixed ~15 typos and grammatical errors (searech, defaukt, produciton, configuraiton, retreiving, alowed, is differs, etc.)
  • Branding: Corrected "Paypal" → "PayPal" in headings and body text
  • Changelog date: v2.6.26 date corrected from 2026-02-26 to 2026-02-27 to match the actual merge date of PR fix(source-paypal-transaction): use 3-digit milliseconds for disputes datetime format (AI-Triage PR) #74027
  • Technical fix: Corrected start_endstart_date in the Search Invoices info block (matches the actual config field name in manifest.yaml)
  • Deprecation notice: Added info block noting that the PayPal Payments API v1 (used by the List Payments stream) is deprecated by PayPal
  • Clarity: Reformatted setup steps 8–10 for readability; tightened caution blocks

Review guide

  1. docs/integrations/sources/paypal-transaction.md — the only file changed

Items worth verifying:

  • The start_endstart_date rename (line 213) — confirm this matches the connector's actual config field
  • The Payments API v1 deprecation notice (lines 223–225) — confirm this is appropriate to surface to users
  • Changelog date correction for v2.6.26 (line 269) — 2026-02-27 matches the merge timestamp of the commit

User Impact

Documentation-only change. No runtime or connector behavior changes. Users get more accurate and readable docs.

Can this PR be safely reverted and rolled back?

  • YES 💚

Note: This PR was created by Devin AI, an automated documentation assistant, based on a review of recent connector changes. Reviewers may merge, modify, or close this PR as they see fit.

Requested by: bot_apk (apk@cognition.ai)
Link to Devin run: https://app.devin.ai/sessions/646f7ec2c9df4e3eb80854b2b5b2e3a2

… date

Co-Authored-By: bot_apk <apk@cognition.ai>
@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@github-actions
Copy link
Contributor

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

  • 🛠️ Quick Fixes
    • /format-fix - Fixes most formatting issues.
    • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
  • ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
    • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
    • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
    • /ai-review - AI-powered PR review for connector safety and quality gates.
  • 🚀 Connector Releases:
    • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
    • /bump-progressive-rollout-version - Bumps connector version with an RC suffix (2.16.10-rc.1) for progressive rollouts (enableProgressiveRollout: true).
      • Example: /bump-progressive-rollout-version changelog="Add new feature for progressive rollout"
  • ☕️ JVM connectors:
    • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
      Example: /update-connector-cdk-version connector=destination-bigquery
    • /bump-bulk-cdk-version bump=patch changelog='foo' - Bump the Bulk CDK's version. bump can be major/minor/patch.
  • 🐍 Python connectors:
    • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
    • /poe source example lock - Alias for /poe connector source-example lock.
    • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
    • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
  • ⚙️ Admin commands:
    • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
      Example: /force-merge reason="CI is flaky, tests pass locally"
📚 Show Repo Guidance

Helpful Resources

📝 Edit this welcome message.

@github-actions
Copy link
Contributor

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-okrrrxduv-airbyte-growth.vercel.app

Built with commit 4d7a6ad.
This pull request is being automatically deployed with vercel-action

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

Labels

area/documentation Improvements or additions to documentation team/documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants