diff --git a/Form-Controls/README.md b/Form-Controls/README.md
index bfcdf6c0b..54d27d2c5 100644
--- a/Form-Controls/README.md
+++ b/Form-Controls/README.md
@@ -30,18 +30,18 @@ Do not write a form action for this project.
 
 Let's write out our testable criteria. Check each one off as you complete it.
 
-- [ ] I have used HTML only.
+- [x] I have used HTML only.
 - [x] I have not used any CSS or JavaScript.
 
 ### HTML
 
-- [ ] My form is semantic html.
-- [ ] All inputs have associated labels.
-- [ ] My Lighthouse Accessibility score is 100.
-- [ ] I require a valid name. I have defined a valid name as a text string of two characters or more.
-- [ ] I require a valid email.
-- [ ] I require one colour from a defined set of 3 colours.
-- [ ] I require one size from a defined set of 6 sizes.
+- [x] My form is semantic html.
+- [x] All inputs have associated labels.
+- [x] My Lighthouse Accessibility score is 100.
+- [x] I require a valid name. I have defined a valid name as a text string of two characters or more.
+- [x] I require a valid email.
+- [x] I require one colour from a defined set of 3 colours.
+- [x] I require one size from a defined set of 6 sizes.
 
 ## Resources
 
diff --git a/Form-Controls/index.html b/Form-Controls/index.html
index 65a866cdb..2fe6ac6cf 100644
--- a/Form-Controls/index.html
+++ b/Form-Controls/index.html
@@ -3,25 +3,109 @@
   <head>
     <meta charset="utf-8" />
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
-    <title>My form exercise</title>
+    <title>My T-shirt form exercise</title>
     <meta name="description" content="" />
     <meta name="viewport" content="width=device-width, initial-scale=1" />
   </head>
   <body>
     <header>
-      <h1>Product Pick</h1>
+      <h1>T-shirt Picker</h1>
     </header>
     <main>
-      <form>
+      <form action="/my-handling-form-page" method="post">
         <!-- write your html here-->
         <!-- 
           try writing out the requirements first as comments
         this will also help you fill in your PR message later-->
+
+        <!-- 
+        NB HTML only - no CSS no JS
+
+        1/ log customer name 
+        2/ validate customer name: a text string of two characters or more
+        3/ log customer email
+        4/ validate customer email (format)
+        5/ offer 3 T-shirt colour choices
+        6/ input must pick one
+        7/ offer 6 sizes: XS, S, M, L, XL, XXL
+        8/ input must pick one 
+        -->
+
+        <!--
+        1/ log customer name 
+        2/ validate customer name: a text string of two characters or more
+        -->
+ <p>
+    <label for="name">
+      Name: <input type="text" id="name" min="2" name="user_name" autofocus />
+      </label>
+  </p>
+        <!--
+        3/ log customer email
+        4/ validate customer email (format)
+        -->
+<p>
+    <label for="email">
+      Email: <input type="email" id="email" name="user_email" />
+    </label>
+  </p>
+        <!--
+        5/ offer 3 T-shirt colour choices
+        6/ input must pick one
+        -->
+ <fieldset>
+    <legend>T-shirt colour</legend>
+    <p>
+      <input type="radio" name="color" id="colour_1" value="blue" />
+      <label for="colour_1">blue</label>
+    </p>
+    <p>
+      <input type="radio" name="color" id="colour_2" value="black" />
+      <label for="colour_2">black</label>
+    </p>
+    <p>
+      <input type="radio" name="color" id="colour_3" value="purple" />
+      <label for="colour_3">purple</label>
+    </p>
+ </fieldset>
+        <!--
+        7/ offer 6 sizes: XS, S, M, L, XL, XXL
+        8/ input must pick one 
+        -->
+ <fieldset>
+    <legend>T-shirt size</legend>
+    <p>
+      <input type="radio" name="size" id="size_1" value="XS" />
+      <label for="size_1">XS</label>
+    </p>
+    <p>
+      <input type="radio" name="size" id="size_2" value="S" />
+      <label for="size_2">S</label>
+    </p>
+    <p>
+      <input type="radio" name="size" id="size_3" value="M" />
+      <label for="size_3">M</label>
+    </p><p>
+      <input type="radio" name="size" id="size_4" value="L" />
+      <label for="size_4">L</label>
+    </p>
+    <p>
+      <input type="radio" name="size" id="size_5" value="XL" />
+      <label for="size_5">XL</label>
+    </p>
+    <p>
+      <input type="radio" name="size" id="size_6" value="XXL" />
+      <label for="size_6">XXL</label>
+    </p>
+ </fieldset>  
+ <p></p>     
+<input type="submit" value="Submit">
+<input type="reset" value="Reset">
       </form>
     </main>
     <footer>
       <!-- change to your name-->
-      <h2>By HOMEWORK SOLUTION</h2>
+      <h2>Form by Miriam Jorna</h2>
     </footer>
   </body>
 </html>
diff --git a/Wireframe/README.md b/Wireframe/README.md
index f7b59df8c..8134a757a 100644
--- a/Wireframe/README.md
+++ b/Wireframe/README.md
@@ -14,11 +14,11 @@ There are some provided HTML and CSS files you can use to get started. You can u
 
 <!--{{<objectives>}}>-->
 
-- [ ] Use semantic HTML tags to structure the webpage
-- [ ] Create three articles, each including an image, title, summary, and a link
-- [ ] Check a webpage against a wireframe layout
-- [ ] Test web code using [Lighthouse](https://programming.codeyourfuture.io/guides/testing/lighthouse)
-- [ ] Use version control by committing often and pushing regularly to GitHub
+- [x] Use semantic HTML tags to structure the webpage
+- [x] Create three articles, each including an image, title, summary, and a link
+- [x] Check a webpage against a wireframe layout
+- [x] Test web code using [Lighthouse](https://programming.codeyourfuture.io/guides/testing/lighthouse)
+- [x] Use version control by committing often and pushing regularly to GitHub
 <!--{{</objectives>}}>-->
 
 ## Acceptance Criteria
diff --git a/Wireframe/book.jpg b/Wireframe/book.jpg
new file mode 100644
index 000000000..9e314740d
Binary files /dev/null and b/Wireframe/book.jpg differ
diff --git a/Wireframe/github-cat.png b/Wireframe/github-cat.png
new file mode 100644
index 000000000..267a20327
Binary files /dev/null and b/Wireframe/github-cat.png differ
diff --git a/Wireframe/index.html b/Wireframe/index.html
index 0e014e535..ff49854b1 100644
--- a/Wireframe/index.html
+++ b/Wireframe/index.html
@@ -1,32 +1,80 @@
 <!DOCTYPE html>
 <html lang="en">
+  <title>Wireframe, Readme file and Github branches explained</title>
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
     <title>Wireframe</title>
     <link rel="stylesheet" href="style.css" />
   </head>
+    
   <body>
     <header>
-      <h1>Wireframe</h1>
+      <h1>Wireframe, Readme file and Github branches explained</h1>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        This is the header, meant to give an overview of what can be found on this page.
       </p>
     </header>
+    
     <main>
+      <table>
+
+    <tr>
+      <td width="100%" colspan="2">
+<section>
       <article>
-        <img src="placeholder.svg" alt="" />
-        <h2>Title</h2>
+        <img src="wireframe.png" alt="a wireframe sketch of this page"/>
+        <h2>Wireframe</h2>
         <p>
-          Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
-          voluptates. Quisquam, voluptates.
+         A wireframe is a sketch of the design of a webpage. It is helpful in order to 
+         plan the page lay-out and usability.
         </p>
-        <a href="">Read more</a>
+        <a href="./wireframe-wireframe.html">Read more</a>
       </article>
+      </section>
+      
+    </td>
+  </tr>
+        <tr>
+          <td class="left">
+       
+      <section>
+      <article>
+        <img src="book.jpg" alt="the Gutenberg Bible is the oldest printed book" />
+        <h2>Readme files</h2>
+        <p>
+          This article should be on the left side of the page and discuss the usefulness of a Readme file.<br>
+          Readme files are designed to help a page designer figure out 
+          what needs to be done and how they are expected to go about it.
+        </p>
+        <a href="./wireframe-readme.html">Read more</a>
+      </article>
+      </section>
+    </td>
+  
+    <td class="right">  
+<section>
+      <article>
+        <img src="github-cat.png" alt="the Github logo" />
+        <h2>Github branches</h2>
+        <p>
+          Github branches are elements of a project on Github. Everyone working on a project should make a new branch 
+          for any small or big change alike. They help keeping track of changes, specifically when working
+          on a project with several people.  
+        </p>
+        <a href="./wireframe-github.html">Read more</a>
+      </article>
+      </section>
+      </td>
+    </tr>
+
+
+      </table>
     </main>
     <footer>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        The footer is where normally more information about the organisation behind the 
+        website can be found, such as contact details/street address and who they are.
       </p>
     </footer>
   </body>
diff --git a/Wireframe/style.css b/Wireframe/style.css
index be835b6c7..a88713852 100644
--- a/Wireframe/style.css
+++ b/Wireframe/style.css
@@ -37,7 +37,7 @@ a {
   max-width: fit-content;
 }
 img,
-svg {
+png {
   width: 100%;
   object-fit: cover;
 }
@@ -49,9 +49,36 @@ main {
   max-width: var(--container);
   margin: 0 auto calc(var(--space) * 4) auto;
 }
+
+table {
+  font-family: Arial, Helvetica, sans-serif;
+  border-collapse: collapse;
+  width: 100%;
+}
+
+td, th {
+  border: 1px solid #ddd;
+  padding: 8px;
+}
+
+tr:nth-child(even){background-color: #f2f2f2;}
+
+tr:hover {background-color: #ddd;}
+
+th {
+  padding-top: 12px;
+  padding-bottom: 12px;
+  text-align: left;
+  background-color: #04AA6D;
+  color: white;
+}
+</style>
+
 footer {
   position: fixed;
   bottom: 0;
+  left: 0;
+  width: 100%;
   text-align: center;
 }
 /* ====== Articles Grid Layout ====

+ - - Title + + Wireframe - Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam, - voluptates. Quisquam, voluptates. + A wireframe is a sketch of the design of a webpage. It is helpful in order to + plan the page lay-out and usability. - Read more + Read more + + +
+ + + + + Readme files + + This article should be on the left side of the page and discuss the usefulness of a Readme file. + Readme files are designed to help a page designer figure out + what needs to be done and how they are expected to go about it. + + Read more + + +	+ + + + Github branches + + Github branches are elements of a project on Github. Everyone working on a project should make a new branch + for any small or big change alike. They help keeping track of changes, specifically when working + on a project with several people. + + Read more + + +