[PATCH 4 of 4] profiling: Documenting new .hgrc options profiling.{output, format}

[timeless]

> +      When printing on stderr, a profiling report is printed.

printing to

> +      When saving to a file, profiling data is saved in python

Personally, i'd write Python with a capital P, but i'm not certain
about conventions here.

> +      pstats.Stats format.

> +      When outputing to a file, kcachegrind can directly import the

I'd avoid writing "outputing" if possible. But this doesn't make
sense, could you please explain?

> +      generated file.
> +    lsprof;;
> +      Use lsprof for profiling, generates a text report.

use a semicolon (;) or dash (-), not a comma (,).

> +      When outputing to a file, the report is saved, not the profiling data.

not => instead of

> +  output;;
> +    File path where profiling data or profiling report should be saved.

'the profiling data or report'

> +    If the file exists, it is erased.

replaced