Fix a few typos

2 files changed, 5 insertions, 5 deletions

diff --git a/README.md b/README.md
index 2ca3942..75b3d62 100644
--- a/README.md
+++ b/README.md
@@ -160,7 +160,7 @@ It's worth emphasizing that none of these encryption solutions protect unlocked
 encrypted files from other users on the same system (that's the job of OS-level
 access control, such as UNIX file permissions), or from the cloud provider you
 may be running a virtual machine on.  By themselves, they also do not protect
-from "evil maid" attacks, i.e. non-permanant offline compromises of the disk.
+from "evil maid" attacks, i.e. non-permanent offline compromises of the disk.
 
 ## Features
 
diff --git a/pam/pam.go b/pam/pam.go
index f79e2d4..dab4a55 100644
--- a/pam/pam.go
+++ b/pam/pam.go
@@ -79,7 +79,7 @@ func (h *Handle) getData(name string) (unsafe.Pointer, error) {
 	return data, h.err()
 }
 
-// ClearData remotes the PAM data with the specified name.
+// ClearData removes the PAM data with the specified name.
 func (h *Handle) ClearData(name string) error {
 	return h.setData(name, unsafe.Pointer(C.CString("")), C.CleanupFunc(C.freeData))
 }
@@ -92,8 +92,8 @@ func (h *Handle) SetSecret(name string, secret unsafe.Pointer) error {
 }
 
 // GetSecret returns a pointer to the C string PAM data with the specified name.
-// This a pointer directory to the data, so it shouldn't be modified. It should
-// have been previously set with SetSecret().
+// This is a pointer directly to the data, so it shouldn't be modified. It
+// should have been previously set with SetSecret().
 func (h *Handle) GetSecret(name string) (unsafe.Pointer, error) {
 	return h.getData(name)
 }
@@ -174,7 +174,7 @@ func (h *Handle) InfoMessage(message string) {
 }
 
 // Transaction represents a wrapped pam_handle_t type created with pam_start
-// form an application.
+// from an application.
 type Transaction Handle
 
 // Start initializes a pam Transaction. End() should be called after the