From 1b686ee8606a76ddb964e98c7451b74c2146a398 Mon Sep 17 00:00:00 2001
From: Tuncer Ayaz
Date: Thu, 15 Mar 2012 13:42:22 +0100
Subject: Fix various comment typos for R16
---
erts/emulator/beam/code_ix.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/erts/emulator/beam/code_ix.h b/erts/emulator/beam/code_ix.h
index bc10e956f5..e2bd0da112 100644
--- a/erts/emulator/beam/code_ix.h
+++ b/erts/emulator/beam/code_ix.h
@@ -18,7 +18,7 @@
*/
/* Description:
- * This is the interface that facilitate changing the beam code
+ * This is the interface that facilitates changing the beam code
* (load,upgrade,delete) while allowing executing Erlang processes to
* access the code without any locks or other expensive memory barriers.
*
@@ -35,7 +35,7 @@
* The third code index is not explicitly used. It can be thought of as
* the "previous active" or the "next staging" index. It is needed to make
* sure that we do not reuse a code index for staging until we are sure
- * that no executing BIFs are still referring it.
+ * that no executing BIFs are still referencing it.
* We could get by with only two (0 and 1), but that would require that we
* must wait for all schedulers to re-schedule before each code change
* operation can start staging.
--
cgit v1.2.3
From 6f3a9107e716c1e7b394876d505fb27d9465ba9b Mon Sep 17 00:00:00 2001
From: Tuncer Ayaz
Date: Fri, 20 Jul 2012 19:27:34 +0200
Subject: Fix various typos in HOWTO/ for R16
---
HOWTO/BENCHMARKS.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/HOWTO/BENCHMARKS.md b/HOWTO/BENCHMARKS.md
index b3df4638ea..28a590dfd2 100644
--- a/HOWTO/BENCHMARKS.md
+++ b/HOWTO/BENCHMARKS.md
@@ -18,13 +18,13 @@ benchmarks you have to [install the tests][]. To get a listing of all
benchmarks you have available call `ts:benchmarks()`.
To run all benchmarks call `ts:bench()`. This will run all benchmarks using
-the emulator which is in you `$PATH` (Note that this does not have to be the
+the emulator which is in your `$PATH` (Note that this does not have to be the
same as from which the benchmarks were built from). All the results of the
benchmarks are put in a folder in `$TESTROOT/test_server/` called
`YYYY_MO_DDTHH_MI_SS`.
Each benchmark is run multiple times and the data for all runs is collected in
-the files within the benchmark folder. All benchmarks are written so that a
+the files within the benchmark folder. All benchmarks are written so that
higher values are better.
Writing benchmarks
--
cgit v1.2.3
From 2efdc7b6867e53760e870cdcb4821f42cf96d417 Mon Sep 17 00:00:00 2001
From: Tuncer Ayaz
Date: Wed, 5 Sep 2012 12:56:59 +0200
Subject: Fix various doc typos for R16
---
lib/tools/doc/src/xref.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/tools/doc/src/xref.xml b/lib/tools/doc/src/xref.xml
index 17de66bb22..9706ae6746 100644
--- a/lib/tools/doc/src/xref.xml
+++ b/lib/tools/doc/src/xref.xml
@@ -1453,7 +1453,7 @@ Evaluates a predefined analysis.
Note however that the code path will be traversed once for
each used library module while setting up module data.
On the other hand, if there are only a few modules that are
- used by not analyzed, using code_path may be faster
+ used but not analyzed, using code_path may be faster
than setting the library path to code:get_path().
If the library path is set to code_path, the set of
--
cgit v1.2.3