Update personal-dashboard-quickstart.md on repo link access

[1of1jey]

finding repository links

it has been very difficult to find repository links as a beginner

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• [ ] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• [ ] The changes in this PR meet the docs fundamentals that are required for all content.
• [ ] All CI checks are passing and the changes look good in the review environment.

[welcome[bot]]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions[bot]]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
account-and-profile/get-started/personal-dashboard-quickstart.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@1of1jey Thanks for opening a~n issue~ PR! ~Could you expand on this a little for me? Is this a problem for you in the documentation or across the site? Which repositories are you trying to find?~

Edit: Oof, sorry, this looked like an issue from what you were asking, and it honestly probably would have been better as an issue first, since I'm not sure this article is where we would want to place this information. I'll look into it, though, make sure it's not hiding somewhere else, and get back to you.