fix: link

[nash1111]

User description

Why

Closes

What

---

PR Type

bug fix, documentation

---

Description

• Fixed naming inconsistencies in playwright.config.ts for device configurations.
• Updated screenshot links in README.md to match the new device configuration names.
• Fixed broken links for MobileSafari and Desktop screenshots.

---

Changes walkthrough 📝

	Relevant files
Bug fix	playwright.config.ts Fix naming inconsistencies in device configurations.          playwright.config.ts Fixed naming inconsistencies for device configurations. Changed Mobile Safari to MobileSafari. Changed Dark Desktop to DarkDesktop. +2/-2
Documentation	README.md Update screenshot links in README to match new names.        README.md Updated screenshot links to match new device configuration names. Fixed broken links for MobileSafari and Desktop screenshots. +2/-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]	2
🧪 Relevant tests	No
🔒 Security concerns	No
⚡ Key issues to review	None

[github-actions[bot]]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Ensure consistent naming conventions for device configurations ___ **Consider using consistent naming conventions for device configurations. The previous names used spaces ("Mobile Safari", "Dark Desktop"), while the new names do not ("MobileSafari", "DarkDesktop"). This inconsistency might lead to confusion or errors in other parts of the codebase where these names are used.** [playwright.config.ts [12-21]](https://github.com/nash1111/nash1111-tech-blog/pull/100/files#diff-f679bf1e58e8dddfc6cff0fa37c8e755c8d2cfc9e6b5dc5520a5800beba59a92R12-R21) ```diff { - name: "MobileSafari", + name: "Mobile Safari", use: { ...devices["iPhone 13"], }, }, { - name: "DarkDesktop", + name: "Dark Desktop", use: { ...devices["Desktop Chrome"], colorScheme: "dark", }, } ``` Suggestion importance[1-10]: 8 Why: The suggestion addresses a maintainability issue by advocating for consistent naming conventions, which can prevent confusion and potential errors in the codebase. This is a significant improvement for code readability and maintainability.	8
Possible issue	Verify and correct the formatting of image URLs in the README ___ **Ensure that the image URLs are correctly formatted and do not contain any breaks or errors. The previous URL for the "Blog Page (iPhone size)" was broken into two lines, which could have caused rendering issues. Verify that the new URLs are accessible and render correctly in the README.** [README.md [12-14]](https://github.com/nash1111/nash1111-tech-blog/pull/100/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R12-R14) ```diff + + - ``` Suggestion importance[1-10]: 7 Why: The suggestion highlights a potential rendering issue due to broken URLs in the README. Ensuring URLs are correctly formatted is important for documentation accuracy and usability, though it is a minor fix.	7