fix: link

[nash1111]

User description

Why

Closes

What

---

PR Type

documentation

---

Description

• Updated the URLs for the blog page and task page screenshots in the README.md file.
• Changed the filenames to reflect specific browsers (Mobile Safari, Chromium).

---

Changes walkthrough 📝

	Relevant files
Documentation	README.md Update screenshot URLs and filenames in README                      README.md Updated URLs for blog page and task page screenshots. Changed filenames to reflect specific browsers (Mobile Safari, Chromium). +4/-3

---

💡 PR-Agent usage: Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions[bot]]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review [1-5]	1
🧪 Relevant tests	No
🔒 Security concerns	No
⚡ Key issues to review	None

[github-actions[bot]]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible bug	Fix the broken image URL by removing the line break ___ **Ensure that the image URLs are correctly formatted and do not contain line breaks. The URL for the 'Blog Page (iPhone size)' image seems to be broken into two lines, which might cause it to not display properly.** [README.md [12-13]](https://github.com/nash1111/nash1111-tech-blog/pull/99/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R12-R13) ```diff - + ``` Suggestion importance[1-10]: 10 Why: The suggestion addresses a critical issue where the image URL is broken into two lines, which would prevent the image from displaying properly. Fixing this is crucial for the correct rendering of the README.	10
Best practice	Standardize the naming convention of screenshot files for clarity and maintainability ___ **Consider using a consistent naming convention for screenshot files. The file names in the URLs vary (e.g., 'blog-page-Mobile-Safari.png' vs 'blog-chromium.png'). Standardizing file names can improve maintainability and clarity.** [README.md [12-15]](https://github.com/nash1111/nash1111-tech-blog/pull/99/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R12-R15) ```diff - - + + ``` Suggestion importance[1-10]: 8 Why: Consistent naming conventions improve maintainability and clarity. This is a good practice and the suggestion is relevant and correctly derived from the PR code diff.	8
Enhancement	Enhance the alt text for images to provide better context and accessibility ___ **Update the alt text for images to include more descriptive information. This can improve accessibility and SEO. For example, the alt text for the 'Blog Page (Desktop)' image could be more descriptive.** [README.md [15]](https://github.com/nash1111/nash1111-tech-blog/pull/99/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R15-R15) ```diff - + ``` Suggestion importance[1-10]: 7 Why: Improving the alt text enhances accessibility and SEO, which is beneficial but not critical. The suggestion is accurate and contextually appropriate.	7
Accessibility	Ensure that the image URLs are accessible to all users ___ **Verify the accessibility of the image URLs. Ensure that the repository settings allow these images to be viewed publicly, as private or incorrect settings might prevent the images from being accessible.** [README.md [12-17]](https://github.com/nash1111/nash1111-tech-blog/pull/99/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R12-R17) ```diff + + - ``` Suggestion importance[1-10]: 5 Why: While ensuring accessibility is important, this suggestion is more of a reminder and does not directly improve the code. It is still a valid point but less impactful compared to the other suggestions.	5