Skip to content

Fix: Correct image path typo in Payment Request Formats guide #1177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kilavvy
Copy link

@kilavvy kilavvy commented Jun 22, 2025

Description

This PR fixes a typo in the image paths on the Payment Request Formats page. The paths were pointing to misspelled filenames (adresses instead of addresses), causing the images to not display correctly.

Changes:

  • Updated image paths in guide/how-it-works/payment-request-formats.md to use the correct spelling "addresses".

Copy link

netlify bot commented Jun 22, 2025

Deploy Preview for bitcoin-design-site ready!

Name Link
🔨 Latest commit c93c102
🔍 Latest deploy log https://app.netlify.com/projects/bitcoin-design-site/deploys/6857d981d9f4aa0008c7f0e0
😎 Deploy Preview https://deploy-preview-1177--bitcoin-design-site.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@GBKS
Copy link
Contributor

GBKS commented Jun 23, 2025

Hi, thanks for making this fix. Are you using a bot/AI for this? We're seeing a pattern here of new contributors posting minor typo fixes, from private accounts and hundreds of repositories - like yours. Certainly looks like automation. Can you share some background on your contribution, please?

@kilavvy
Copy link
Author

kilavvy commented Jun 23, 2025

Hi, thanks for making this fix. Are you using a bot/AI for this? We're seeing a pattern here of new contributors posting minor typo fixes, from private accounts and hundreds of repositories - like yours. Certainly looks like automation. Can you share some background on your contribution, please?

Hi! Yes, I am using AI tools to help identify and fix minor issues like typos across open source repositories. My goal is to contribute to the overall quality and readability of the documentation and code.

@GBKS
Copy link
Contributor

GBKS commented Jun 23, 2025

@kilavvy cool. Which ones do you use? Maybe we should adopt this in our process.

@kilavvy
Copy link
Author

kilavvy commented Jun 23, 2025

@kilavvy cool. Which ones do you use? Maybe we should adopt this in our process.

Haha, I wish there was some secret benefit for me! 😄
Actually, I just use misspell to catch common typos automatically. It’s a simple but handy tool!

@GBKS
Copy link
Contributor

GBKS commented Jun 23, 2025

Haha, I wish there was some secret benefit for me!

The benefit of not having to spend time on typos but work on cooler things? 😄

Copy link
Contributor

@GBKS GBKS left a comment

Choose a reason for hiding this comment

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

So this PR actually breaks an image path, instead of fixing it. Problem is that both the path and the image file name have the typo. So in order for this PR to work, the file name would also have to be fixed.

@kilavvy mentioned they use misspell to automatically identify typos. That library probably just looks at the markdown file and does not double-check against the file names.

Copy link
Collaborator

@swedishfrenchpress swedishfrenchpress left a comment

Choose a reason for hiding this comment

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

image Breaks image path. Image files will need to be renamed before merge.

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.

3 participants