@@ -22,7 +22,9 @@ <h2>The purpose of a README file</h2>
2222 is often the first thing that users see when they visit a project's repository, so it is important
2323 to make it clear and informative.
2424 </ p >
25- < a href =""> Read more</ a >
25+ < a href ="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes ">
26+ Read more about README files
27+ </ a >
2628 </ article >
2729 < article >
2830 < img src ="images/wireframe.png " alt ="" />
@@ -32,7 +34,9 @@ <h2>The purpose of a wireframe</h2>
3234 or an application’s user interface (UI) and core functionality. It shows where
3335 components should be in relation to each other and what, roughly, they should do.
3436 </ p >
35- < a href =""> Read more</ a >
37+ < a href ="https://www.experienceux.co.uk/faqs/what-is-wireframing/ "
38+ > Read more about wireframing
39+ </ a >
3640 </ article >
3741 < article >
3842 < img src ="images/Git-logo.svg " alt ="" />
@@ -44,7 +48,9 @@ <h2>Branch in Git</h2>
4448 work on new features, fix bugs, or experiment with changes without affecting the main
4549 codebase until you are ready to merge your changes back in.
4650 </ p >
47- < a href =""> Read more</ a >
51+ < a href ="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches ">
52+ Read more about branches in Git
53+ </ a >
4854 </ article >
4955 </ main >
5056 < footer >
0 commit comments