diff --git a/pcapgo/ngread.go b/pcapgo/ngread.go
index 16aabb900..0734ea89d 100644
--- a/pcapgo/ngread.go
+++ b/pcapgo/ngread.go
@@ -123,14 +123,14 @@ func (r *NgReader) getUint64(buffer []byte) uint64 {
 
 // Now the pcapng implementation
 
-// readBlock reads a the blocktype and length from the file. If the type is a section header, endianess is also read.
+// readBlock reads a the blocktype and length from the file. If the type is a section header, endianness is also read.
 func (r *NgReader) readBlock() error {
 	if err := r.readBytes(r.buf[0:8]); err != nil {
 		return err
 	}
 	r.currentBlock.typ = ngBlockType(r.getUint32(r.buf[0:4]))
-	// The next part is a bit fucked up since a section header could change the endianess...
-	// So first read then length just into a buffer, check if its a section header and then do the endianess part...
+	// The next part is a bit fucked up since a section header could change the endianness...
+	// So first read then length just into a buffer, check if its a section header and then do the endianness part...
 	if r.currentBlock.typ == ngBlockTypeSectionHeader {
 		if err := r.readBytes(r.buf[8:12]); err != nil {
 			return err
diff --git a/pfring/pfring.go b/pfring/pfring.go
index b9b8fb0ab..b95f5e49d 100644
--- a/pfring/pfring.go
+++ b/pfring/pfring.go
@@ -27,7 +27,7 @@ struct metadata {
 // struct (struct metadata above).
 // Another way to do this, would be to store the struct offsets in defines
 // and use encoding/binary in go-land. But this has the downside, that there is
-// no native endianess in encoding/binary and storing ByteOrder in a variable
+// no native endianness in encoding/binary and storing ByteOrder in a variable
 // leads to an expensive itab lookup + call (instead of very fast inlined and
 // optimized movs). Using unsafe magic could lead to problems with unaligned
 // access.