Updated 047 Tutorial on forking JCB snippets so you can share your snippets with the rest of the Community (markdown)

047-Tutorial-on-forking-JCB-snippets-so-you-can-share-your-snippets-with-the-rest-of-the-Community.md

@@ -119,12 +119,13 @@ The next commit message I'm just going to say `git commit -m Updated the FooTabl
 
 [00:25:41](https://www.youtube.com/watch?v=0hgHeQVTLOk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h25m41s)
 
-Now we want to add the accordion which is the new snippet. It is just `git add` and we can select the file name `'Uikit v3 - Collapse) Accordion.json'`. There is a shortcut to this, it is when you use the `.git.add` and that is usually when you have lots of files and just want to add them all. It is like I explained if you are doing a whole bunch of snippets for a specific library. I would suggest doing library per library instead of just mixing them all up. [00:26:10](https://www.youtube.com/watch?v=0hgHeQVTLOk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h26m10s) Because if we target a library and add a bunch of snippets for it and then have a commit message just for that, then we could explain that within the commit message, that it is for the specific library and so forth because usually with new libraries it is good for us to take it one step at a time. That file has been added. We just have to add a commit message for it. I'm just going to say `'Added the accordion snippet for Uikit v3 as a demonstration on how this should work.'` [00:26:46](https://www.youtube.com/watch?v=0hgHeQVTLOk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h26m46s)  Then just again sign off that commit.` git status`.<<<<<<<<<<
+Now we want to add the accordion which is the new snippet. It is just `git add` and we can select the file name `'Uikit v3 - Collapse) Accordion.json'`. There is a shortcut to this, it is when you use the `.git.add` and that is usually when you have lots of files and just want to add them all. It is like I explained if you are doing a whole bunch of snippets for a specific library. I would suggest doing library per library instead of just mixing them all up. [00:26:10](https://www.youtube.com/watch?v=0hgHeQVTLOk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h26m10s) Because if we target a library and add a bunch of snippets for it and then have a commit message just for that, then we could explain that within the commit message, that it is for the specific library and so forth because usually with new libraries it is good for us to take it one step at a time. That file has been added. We just have to add a commit message for it. I'm just going to say `'Added the accordion snippet for Uikit v3 as a demonstration on how this should work.'` [00:26:46](https://www.youtube.com/watch?v=0hgHeQVTLOk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h26m46s)  Then just again sign off that commit.` git status`.
+ We have one file left and already have three commits ahead of the branch that we have cloned. [00:27:10](https://www.youtube.com/watch?v=0hgHeQVTLOk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h27m10s) So just this last file which is the update we have made. We're going to first add the file `git add 'Uikit v2 - (Layout) Form.json'` and then add a commit message to explain what we did.` git commit -m "Added usage paragraph to explain how to use the 'Uikit v2 - (Layout) Form.json'`. Writing out the file name like that is clear enough [00:27:38](https://www.youtube.com/watch?v=0hgHeQVTLOk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h27m38s) and enter. Again just sign off on that. If you do not have keys, go Google this. Start signing your request. But at this stage, it is not a requirement. If we do `git status` we will see that we are 4 commits ahead.<<<<<< 
+
 
 
 
 
- We'll see we've got one file left and we already have three commits ahead of the branch that we have cloned. [00:27:10](https://www.youtube.com/watch?v=0hgHeQVTLOk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h27m10s) So just this last file which is the update we made. We're going to first add the file git add 'Uikit v2 - (Layout) Form.json' and then add a commit message to explain what we did. git commit -m "Added usage paragraph to explain how to use the 'Uikit v2 - (Layout) Form.json'. Writing out the file name like that is clear enough [00:27:38](https://www.youtube.com/watch?v=0hgHeQVTLOk&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h27m38s) and enter. Again just sign off on that. Again if you don't have keys, go Google this. Start signing your request. But at this stage, it's not a requirement as I said. If we do git status we'll see that we are 4 commits ahead. 
 
 ### Configuring A Remote For A Fork