<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -215,8 +215,9 @@ passing a hash produces a list of key/value pairs:
 
 The C&lt;show_pets()&gt; function works because the C&lt;%pet_names_and_types&gt; hash
 flattens into the list C&lt;'Lucky', 'dog', 'Rodney', 'dog', 'Tuxedo', 'cat',
-'Petunia', 'cat'&gt;.  The assignment within C&lt;show_pets()&gt; works effectively as
-the assignment to C&lt;%pet_names_and_types&gt; does.
+'Petunia', 'cat'&gt;. The hash assignment inside the function C&lt;show_pets()&gt; 
+works essentially as the more explicit assignment to C&lt;%pet_names_and_types&gt;
+does.
 
 This is often useful, but there are limitations to understand.  If you wish to
 make a C&lt;show_pets_of_type()&gt; function, where one parameter is the I&lt;type&gt; of
@@ -231,8 +232,8 @@ C&lt;pop&gt; to remove it from the end of C&lt;@_&gt;):
 
         while (my ($name, $species) = each %pets)
         {
-            B&lt;next unless $species eq $type;&gt;
-            say &quot;$name is a $species&quot;;
+            B&lt;next unless $species eq $type;&gt;   ## Isn't using 'unless' frowned upon?
+            say &quot;$name is a $species&quot;;          ## according to PBP? (jeremiah)
         }
     }
 
@@ -314,7 +315,7 @@ modules on the CPAN for declarative parameter handling.
 Defensive programming often benefits from checking types and values of
 arguments for appropriateness before performing further processing.  By
 default, Perl 5 provides few built-in mechanisms for doing so (in some cases,
-L&lt;prototypes&gt; can I&lt;help&gt;, but that's not their primary purpose).  You can
+L&lt;prototypes&gt; can I&lt;help&gt;, but that's not their primary purpose). You can
 check that the I&lt;number&gt; of parameters passed to a function is correct by
 evaluating C&lt;@_&gt; in scalar context:
 
@@ -373,8 +374,9 @@ names:
 
 Functions in namespaces are I&lt;visible&gt; outside of those namespaces in the sense
 that you can refer to them directly, but they are only callable by their short
-names from within the namespace, unless you have somehow made them available to
-the current namespace by a process called importing and exporting.
+names from within the namespace in which they are declared, unless you have
+somehow made them available to the current namespace through the processes of
+importing and exporting.
 
 =head3 Importing
 
@@ -428,7 +430,7 @@ has compiled the entire statement.
 =for review
 
 Discuss unimporting?  In my experience, it's not nearly as well supported as
-importing.
+importing. (I agree with you, I rarely (okay, never) use it.) (jeremiah)
 
 =end for
 
@@ -438,6 +440,8 @@ importing.
 
 Does this belong instead in the Modules chapter?
 
++1 (jeremiah)
+
 =end for
 
 X&lt;functions; exporting&gt;</diff>
      <filename>sections/functions.pod</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>d57e55b864e5d0b4ea354afc8ee20ba64c1b1741</id>
    </parent>
    <parent>
      <id>99c78c9b3115d1624618d481ef6525055ea3a7e9</id>
    </parent>
  </parents>
  <author>
    <name>chromatic</name>
    <email>chromatic@wgz.org</email>
  </author>
  <url>http://github.com/chromatic/modern_perl_book/commit/cd6ab69edc5e9beaa2a321d52ce9671432822c25</url>
  <id>cd6ab69edc5e9beaa2a321d52ce9671432822c25</id>
  <committed-date>2009-11-05T16:58:26-08:00</committed-date>
  <authored-date>2009-11-05T16:58:26-08:00</authored-date>
  <message>Merge branch 'master' of git://github.com/jeremiah/modern_perl_book into jeremiah/master</message>
  <tree>058a107ca333692780c570cb2def404ddfa62a80</tree>
  <committer>
    <name>chromatic</name>
    <email>chromatic@wgz.org</email>
  </committer>
</commit>
