@@ -16,33 +16,33 @@ <h2>A Wireframe is a simple two dimentional blueprint of a website. </h2>
1616 < img src ="placeholder.svg " alt ="" />
1717 < h2 > The purpose of a README file</ h2 >
1818 < p >
19- A wireframe is a simple line diagram representing the skeleton of a website
20- or an application’s user interface (UI) and core functionality. It shows where
21- components should be in relation to each other and what, roughly, they should do.
19+ A README file is a text file that provides information about a project. It typically
20+ includes instructions on how to install and use the project, as well as any other relevant
21+ information such as the project's purpose, features, and how to contribute. The README file
22+ is often the first thing that users see when they visit a project's repository, so it is important
23+ to make it clear and informative.
2224 </ p >
2325 < a href =""> Read more</ a >
2426 </ article >
2527 < article >
2628 < img src ="placeholder.svg " alt ="" />
2729 < h2 > The purpose of a wireframe</ h2 >
2830 < p >
29- A branch is a sequence of commits in a project. It is a way to work on different
30- versions of a project at the same time. When you create a branch, you are creating
31- a new line of development that diverges from the main codebase. This allows you to
32- work on new features, fix bugs, or experiment with changes without affecting the main
33- codebase until you are ready to merge your changes back in.
31+ A wireframe is a simple line diagram representing the skeleton of a website
32+ or an application’s user interface (UI) and core functionality. It shows where
33+ components should be in relation to each other and what, roughly, they should do.
3434 </ p >
3535 < a href =""> Read more</ a >
3636 </ article >
3737 < article >
3838 < img src ="placeholder.svg " alt ="" />
3939 < h2 > Branch in Git</ h2 >
4040 < p >
41- A README file is a text file that provides information about a project. It typically
42- includes instructions on how to install and use the project, as well as any other relevant
43- information such as the project's purpose, features, and how to contribute. The README file
44- is often the first thing that users see when they visit a project's repository, so it is important
45- to make it clear and informative .
41+ A branch is a sequence of commits in a project. It is a way to work on different
42+ versions of a project at the same time. When you create a branch, you are creating
43+ a new line of development that diverges from the main codebase. This allows you to
44+ work on new features, fix bugs, or experiment with changes without affecting the main
45+ codebase until you are ready to merge your changes back in .
4646 </ p >
4747 < a href =""> Read more</ a >
4848 </ article >
0 commit comments