22
33## Learning Goals
44
5- * Practice writing arrays
6- * Practice using _ destructive_ methods to manipulate arrays
7- * Practice using _ nondestructive_ methods to manipulate arrays
5+ - Practice writing arrays
6+ - Practice using _ destructive_ methods to manipulate arrays
7+ - Practice using _ nondestructive_ methods to manipulate arrays
88
99## Introduction
1010
@@ -31,11 +31,11 @@ accessing and manipulating this array.
3131Near the top of ` indexTest.js ` you will see the following:
3232
3333``` js
34- beforeEach (function () {
35- cats .length = 0 ;
34+ beforeEach (function () {
35+ cats .length = 0 ;
3636
37- cats .push (' Milo' , ' Otis' , ' Garfield' );
38- });
37+ cats .push (" Milo" , " Otis" , " Garfield" );
38+ });
3939```
4040
4141What this code does is _ reset_ the array to its original contents before each
@@ -68,11 +68,11 @@ machine. To preserve your solution on your GitHub fork, you will need to stage t
6868changes you've made, commit them, and push the commit up to GitHub. Use
6969the following commands to do this:
7070
71- ``` sh
72- git add .
73- git commit -m " Completed assignment"
74- git push
71+ ``` console
72+ $ git add .
73+ $ git commit -m " Completed assignment"
74+ $ git push
7575```
7676
7777If you visit your fork on GitHub, you should now see that _ you've_ made the most
78- recent commit, and your code will be present in the files.
78+ recent commit, and your code will be present in the files.
0 commit comments