I made some grammar fixes in faulthandler.rst and tweaked the example to better show what the module does.

I’d like to fix the synopsis too: “dump the Python traceback” is not very clear to me.  It is the traceback or the stack trace?  Why is it called “the” traceback?  Something like “dumping the stack trace on CPython crashes” would be better IMO.

What do you call a "stack trace"? I use this term in the C language, especially when using the "where" command of gdb. In Python, the stack trace is called a "traceback". Anyway, faulthandler prints the Python trace, not the C trace, so I prefer to call it a "traceback" than "stack trace".

faulthandler.dump_traceback() output is similar to:

    try:
        raise ValueError()
    except:
        exctype, value, tb = sys.exc_info()
        traceback.print_tb(tb)

faulthandler doesn't print the line from the script, only the function name, file name and line number; and the first line is different.

> faulthandler prints the Python trace, not the C trace, so I prefer to
> call it a "traceback" than "stack trace".
Okay.  What do you think about this synopsis then: dumping the traceback on CPython crashes?

> dumping the traceback on CPython crashes?

faulthandler is no more specific to crashes: you can dump the tracebacks while Python is running using a signal or an explicit call to faulthandler.dump_traceback().

Okay, I understand now that the traceback always exists, not only during exceptions.  The module gives control over the display of that traceback.  Am I right?

New changeset a97dcdee35f9 by Victor Stinner in branch '3.4':
Issue #12209: Minor edits to faulthandler doc. Patch written by Éric Araujo.
http://hg.python.org/cpython/rev/a97dcdee35f9

New changeset 6f80ca0012ae by Victor Stinner in branch 'default':
(Merge 3.4) Issue #12209: Minor edits to faulthandler doc. Patch written by
http://hg.python.org/cpython/rev/6f80ca0012ae

Sorry for the delay. I applied your patch.

Thanks!