Apply suggestions from code review

nevkontakte · flimzy · nevkontakte · commit adcfc773ebfe · 2022-04-19T11:35:10.000+01:00
See gopherjs#1111. Co-authored-by: Jonathan Hall <flimzy@flimzy.com>
diff --git a/compiler/natives/src/syscall/syscall_js_wasm.go b/compiler/natives/src/syscall/syscall_js_wasm.go
@@ -1,5 +1,3 @@
-//go:build js
-
 package syscall
 
 import (
@@ -39,7 +37,7 @@ func unsetenv_c(k string) {
 
 func setStat(st *Stat_t, jsSt js.Value) {
 	// This method is an almost-exact copy of upstream, except for 4 places where
-	// time stamps are obtained as floats in lieu of int64. Unstread wasm emulates
+	// time stamps are obtained as floats in lieu of int64. Upstream wasm emulates
 	// a 64-bit architecture and millisecond-based timestamps fit within an int
 	// type. GopherJS is 32-bit and use of 32-bit ints causes timestamp truncation.
 	// We get timestamps as float64 (which matches JS-native representation) and
diff --git a/doc/syscalls.md b/doc/syscalls.md
@@ -2,7 +2,7 @@
 
 System calls are the bridge between your application and your operating system. They are used whenever you access something outside of your application's memory, for example when you write to the console, when you read or write files or when you access the network. In Go, system calls are mostly used by the `os` package, hence the name. When using GopherJS you need to consider if system calls are available or not.
 
-Starting with 1.18, GopherJS provides to the same [set of cross-platform](https://pkg.go.dev/syscall?GOOS=js) syscalls as standard Go WebAssembly, emulating them via JavaScript APIs available in the runtime (browser or Node.js).
+Starting with 1.18, GopherJS provides the same [set of cross-platform](https://pkg.go.dev/syscall?GOOS=js) syscalls as standard Go WebAssembly, emulating them via JavaScript APIs available in the runtime (browser or Node.js).
 
 ### Output redirection to console
 
