grammar

[enetdown-web] / dot-plan / posts / 2011 / 08 / 29 / switching_out_web_scraping_modules.mdwn

diff --git a/dot-plan/posts/2011/08/29/switching_out_web_scraping_modules.mdwn b/dot-plan/posts/2011/08/29/switching_out_web_scraping_modules.mdwn
index 888fd77..d2ed1e6 100644 (file)
--- a/dot-plan/posts/2011/08/29/switching_out_web_scraping_modules.mdwn
+++ b/dot-plan/posts/2011/08/29/switching_out_web_scraping_modules.mdwn
@@ -1,3 +1,5 @@
+[[!meta updated="2012-01-31 21:20:04 +0000"]]
+
 I recently had to
 [[change|http://enetdown.org/git/?p=goosebumper;a=commitdiff;h=1671fff2233699f46ccdb8818990d6c9e4231db7]]
 some of the code in my scraping software for Blackboard because newer versions of
@@ -6,7 +8,7 @@ some of the code in my scraping software for Blackboard because newer versions o
 [[WWW::Mechanize::Firefox|http://p3rl.org/WWW::Mechanize::Firefox]]. My
 decision to use `WWW::Mechanize::Firefox` was primarily prompted by ease of
 development. By being able to look at the DOM and match elements using all of
-Firefox's great development tools such [[Firebug|http://getfirebug.com/]], I
+Firefox's great development tools such as [[Firebug|http://getfirebug.com/]], I
 was able to quickly write [[XPath|http://www.w3.org/TR/xpath]] queries to get
 exactly the information I needed. Plus, Firefox would handle all the
 difficulties of recursive frames and JavaScript. This had drawbacks in that it
@@ -15,7 +17,7 @@ successfully which made me hesitant about putting it in a cronjob. It worked,
 but there was something kludgey about the whole thing.
 
 That solution worked last semester, but when I tried it at the beginning of
-this semester, things started breaking down. At first I tried working around
+this semester, things started breaking down. At first, I tried working around
 it, but it was too broken. I needed to use JavaScript, so the only solution I
 could find was [[WWW::Scripter|http://p3rl.org/WWW::Scripter]]. It has a plugin
 system that lets you use two different JavaScript engines: a pure-Perl engine