Minor fix in the 'saveframe' doc

bin/saveframe

@@ -75,7 +75,7 @@ Example Usage:
     => To save a specific frame like `File "dir/mod1.py", line 9, in func2`, use:
     $ saveframe --filename=/path/to/file --frames=mod1.py:9:func2 <script_or_command_to_run>
 
-    => To save the last 3 frames from the bottom, use:
+    => To save the first 3 frames from the bottom, use:
     $ saveframe --frames=3 <script_or_command_to_run>
 
     => To save all the frames from 'mod1.py' and 'mod2.py' files, use:
@@ -164,7 +164,7 @@ def getargs():
              "5. Number of Frames from Bottom:\n"
              "   --frames=num\n"
              "   Example: --frames=5\n"
-             "   Includes the last 'num' frames from the bottom of the stack trace."
+             "   Includes the first 'num' frames from the bottom of the stack trace."
     )
     parser.add_argument(
         "--variables", default=None,

lib/python/pyflyby/_saveframe.py

@@ -1019,7 +1019,7 @@ def saveframe(filename=None, frames=None, variables=None, exclude_variables=None
         5. Number of Frames from Bottom:
            frames=num
            Example: frames=5
-           Includes the last 'num' frames from the bottom of the stack trace.
+           Includes the first 'num' frames from the bottom of the stack trace.
 
       Default behavior if this parameter is not passed:
         - When user is in a debugger (ipdb/pdb): Save the frame the user is