diff options
| author | Glenn Morris <rgm@gnu.org> | 2012-11-20 00:47:57 -0800 |
|---|---|---|
| committer | Glenn Morris <rgm@gnu.org> | 2012-11-20 00:47:57 -0800 |
| commit | 1faaca8ac8e43c1f9fc2ae80771308b2eb20228f (patch) | |
| tree | cf51c7b7915c9232f384258e292e159a6a1d2394 /doc/lispref/debugging.texi | |
| parent | ccba372d5140646db3ea8ce3d928797611a8d89a (diff) | |
| download | emacs-1faaca8ac8e43c1f9fc2ae80771308b2eb20228f.tar.gz | |
Fix typos in previous
Diffstat (limited to 'doc/lispref/debugging.texi')
| -rw-r--r-- | doc/lispref/debugging.texi | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index 53d739f2295..4450d177896 100644 --- a/doc/lispref/debugging.texi +++ b/doc/lispref/debugging.texi @@ -820,9 +820,9 @@ be cleaner to combine them. If your program is working correctly, but you want to make it run more quickly or efficiently, the first thing to do is @dfn{profile} your -code that you know how it is using resources. If you find that one +code so that you know how it is using resources. If you find that one particular function is responsible for a significant portion of the -runtime, you can start by looking for ways to optimize that piece. +runtime, you can start looking for ways to optimize that piece. Emacs has built-in support for this. To begin profiling, type @kbd{M-x profiler-start}. You can choose to profile by processor |