Aleksandr Kuzmenko 5 年 前
コミット
a001fc6861
2 ファイル変更5 行追加5 行削除
  1. 3 3
      std/asys/FileSystem.hx
  2. 2 2
      std/asys/Process.hx

+ 3 - 3
std/asys/FileSystem.hx

@@ -27,9 +27,9 @@ extern class FileSystem {
 		values:
 
 		- `FileAccessMode.Ok` - file is visible to the calling process (it exists)
-		- `FileAccessMode.Execute` - file can be executed by the calling proces
-		- `FileAccessMode.Write` - file can be written to by the calling proces
-		- `FileAccessMode.Read` - file can be read from by the calling proces
+		- `FileAccessMode.Execute` - file can be executed by the calling process
+		- `FileAccessMode.Write` - file can be written to by the calling process
+		- `FileAccessMode.Read` - file can be read from by the calling process
 
 		Mode values can be combined with the bitwise or operator, e.g. calling
 		`access` with the `mode`:

+ 2 - 2
std/asys/Process.hx

@@ -45,14 +45,14 @@ class Process {
 			`writable` specify whether the pipe will be readable and writable from
 			the point of view of the spawned process. If `pipe` is given, it is used
 			directly, otherwise a new pipe is created.
-		- `Ipc` - create an IPC (inter-process comunication) pipe. Only one may be
+		- `Ipc` - create an IPC (inter-process communication) pipe. Only one may be
 			specified in `options.stdio`. This special pipe will not have an entry in
 			the `stdio` array of the resulting process; instead, messages can be sent
 			using the `send` method, and received over `messageSignal`. IPC pipes
 			allow sending and receiving structured Haxe data, as well as connected
 			sockets and pipes.
 
-		Pipes are made available in the `stdio` array afther the process is
+		Pipes are made available in the `stdio` array after the process is
 		spawned. Standard file descriptors have their own variables:
 
 		- `stdin` - set to point to a pipe in index 0, if it exists and is