git » libjio » commit d5715e4

diff --git a/doc/guide.lyx b/doc/guide.lyx
index 4937ae8..364fe8c 100644
--- a/doc/guide.lyx
+++ b/doc/guide.lyx
@@ -491,7 +491,7 @@ The library is completely safe to use in multithreaded applications; however,
 \layout Standard
 
 Most is fully threadsafe so you don't need to worry about concurrency; in
- fact, a lot of effort has been put in making paralell operation safe and
+ fact, a lot of effort has been put in making parallel operation safe and
  fast.
 \layout Standard
 
@@ -504,7 +504,7 @@ jopen()
 \family typewriter 
 jclose()
 \family default 
- in paralell with the same jfs structure, or in the middle of an I/O operation,
+ in parallel with the same jfs structure, or in the middle of an I/O operation,
  just like you do when using the normal UNIX calls.
  In the case of 
 \family typewriter 
diff --git a/doc/guide.txt b/doc/guide.txt
index abc6af4..44ba7d5 100644
--- a/doc/guide.txt
+++ b/doc/guide.txt
@@ -244,11 +244,11 @@ intuitive locking rules you have to bear in mind.
 
 Most is fully threadsafe so you don't need to worry 
 about concurrency; in fact, a lot of effort has been 
-put in making paralell operation safe and fast.
+put in making parallel operation safe and fast.
 
 You need to care only when opening, closing and 
 checking for integrity. In practise, that means that 
-you shouldn't call jopen(), jclose() in paralell with 
+you shouldn't call jopen(), jclose() in parallel with 
 the same jfs structure, or in the middle of an I/O 
 operation, just like you do when using the normal UNIX 
 calls. In the case of jfsck(), you shouldn't invoke it 
diff --git a/doc/tids b/doc/tids
index 02a72d4..43f831f 100644
--- a/doc/tids
+++ b/doc/tids
@@ -25,7 +25,7 @@ holds the maximum transaction ID in use. This file gets opened and mmap()'ed
 for faster use inside jopen(). That way, we can treat it directly as an
 integer holding the max tid.
 
-To avoid paralell modifications, we will always lock the file with fcntl()
+To avoid parallel modifications, we will always lock the file with fcntl()
 before accessing it.
 
 Let's begin by describing how get_tid() works, because it's quite simple: it
diff --git a/tests/performance/Makefile b/tests/performance/Makefile
index c545dc3..36a953f 100644
--- a/tests/performance/Makefile
+++ b/tests/performance/Makefile
@@ -4,10 +4,10 @@ CFLAGS = -Wall -O6
 
 default: all
 
-all: paralell streaming
+all: parallel streaming
 
-paralell: paralell.o
-	$(CC) $(LIBS) paralell.o -o paralell
+parallell: parallel.o
+	$(CC) $(LIBS) parallel.o -o parallel
 
 streaming: streaming.o
 	$(CC) $(LIBS) streaming.o -o streaming
@@ -16,7 +16,7 @@ streaming: streaming.o
 	$(CC) $(CFLAGS) -c $< -o $@
 
 clean:
-	rm -f streaming.o streaming paralell.o paralell
+	rm -f streaming.o streaming parallel.o parallel
 	rm -f *.bb *.bbg *.da *.gcov gmon.out
 
 
diff --git a/tests/performance/paralell.c b/tests/performance/parallel.c
similarity index 92%
rename from tests/performance/paralell.c
rename to tests/performance/parallel.c
index f8f4892..205bb90 100644
--- a/tests/performance/paralell.c
+++ b/tests/performance/parallel.c
@@ -1,6 +1,6 @@
 
 /*
- * streaming.c - A program to test speed of paralell writes using libjio.
+ * streaming.c - A program to test speed of parallel writes using libjio.
  * Alberto Bertogli (albertito@blitiri.com.ar)
  */
 
@@ -19,7 +19,7 @@
 #include <sys/time.h>
 #include <libjio.h>
 
-#define FILENAME "test_file-paralell"
+#define FILENAME "test_file-parallel"
 
 /* Declare here what's shared among threads
  * It's not the cleanest design ever, but let's face it, it's a simple
@@ -30,7 +30,7 @@ int blocksize, towrite, mb;
 
 void help(void)
 {
-	printf("Use: paralell MBs_to_write_per_thread blocksize nthreads\n");
+	printf("Use: parallel MBs_to_write_per_thread blocksize nthreads\n");
 	exit(1);
 }
 
diff --git a/trans.c b/trans.c
index cc7bc54..1effe16 100644
--- a/trans.c
+++ b/trans.c
@@ -574,7 +574,7 @@ int jopen(struct jfs *fs, const char *name, int flags, int mode, int jflags)
 	 * pointer. This means that it must only be held while performing
 	 * operations that depend or alter the file pointer (jread, jreadv,
 	 * jwrite, jwritev), but the others (jpread, jpwrite) are left
-	 * unprotected because they can be performed in paralell as long as
+	 * unprotected because they can be performed in parallel as long as
 	 * they don't affect the same portion of the file (this is protected
 	 * by lockf). The lock doesn't slow things down tho: any threaded app
 	 * MUST implement this kind of locking anyways if it wants to prevent