Skip to content
This repository was archived by the owner on Jan 22, 2020. It is now read-only.

Commit 5e65d61

Browse files
authored
Merge pull request fbaptiste#31 from WillieMaddox/patch-22
Update 02 - Project 3 - Solution - Goal 1.ipynb
2 parents 9653324 + 1874a28 commit 5e65d61

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

Part 2/Section 07 - Project 3/02 - Project 3 - Solution - Goal 1.ipynb

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
"cell_type": "markdown",
1212
"metadata": {},
1313
"source": [
14-
"First we should look at what's in the file itself. Just a few records should be enough. (You can also \"cheat\" and loook in Excel - but this works because the file is relatively small)."
14+
"First we should look at what's in the file itself. Just a few records should be enough. (You can also \"cheat\" and look in Excel - but this works because the file is relatively small)."
1515
]
1616
},
1717
{
@@ -522,7 +522,7 @@
522522
"source": [
523523
"OK, so these seem to work as expected.\n",
524524
"\n",
525-
"We're also to write a string parser - we want to remove any potential leading and trailing spaces."
525+
"We also need to write a string parser - we want to remove any potential leading and trailing spaces."
526526
]
527527
},
528528
{
@@ -668,7 +668,7 @@
668668
"source": [
669669
"To parse each field in a row, I'll first separate the data fields into a list of values, then I'll apply the functions in `column_parsers` to the data in that list. \n",
670670
"\n",
671-
"To do that, I'm going to zip up the parser functions and the data, and use a comprehension to apply each function to it's corresponding data field:"
671+
"To do that, I'm going to zip up the parser functions and the data, and use a comprehension to apply each function to its corresponding data field:"
672672
]
673673
},
674674
{
@@ -728,7 +728,7 @@
728728
"\n",
729729
"Also, the way I have set up the parsers, I only want to look at data where none of the fields are `None` - that's why I had some fields default to an empty string instead of `None` - those are the ones I still want to retain, even if they are empty.\n",
730730
"\n",
731-
"To do this efficiently, I'm going to use `all` from "
731+
"To do this efficiently, I'm going to use `all`"
732732
]
733733
},
734734
{
@@ -2007,7 +2007,7 @@
20072007
"cell_type": "markdown",
20082008
"metadata": {},
20092009
"source": [
2010-
"OK, so mostly the data is clean. Looks like we have a few rows without descriptions, make. \n",
2010+
"OK, so mostly the data is clean. Looks like we have a few rows without descriptions. \n",
20112011
"Technically there's a whole lot more validation and cleaning we should do. For example, it looks like the states are not always proper state abbreviations (like 99 in some records, etc). But this is good enough for now."
20122012
]
20132013
},

0 commit comments

Comments
 (0)