diff --git a/man2/rename.2 b/man2/rename.2
index e782d1048..43310f0f6 100644
--- a/man2/rename.2
+++ b/man2/rename.2
@@ -48,7 +48,7 @@ are also unaffected.
 
 If
 .I newpath
-already exists it will be atomically replaced (subject to
+already exists, it will be atomically replaced (subject to
 a few conditions; see ERRORS below), so that there is
 no point at which another process attempting to access
 .I newpath
@@ -64,7 +64,7 @@ does nothing, and returns a success status.
 
 If
 .I newpath
-exists but the operation fails for some reason
+exists but the operation fails for some reason,
 .BR rename ()
 guarantees to leave an instance of
 .I newpath
@@ -85,9 +85,9 @@ refer to the file being renamed.
 
 If
 .I oldpath
-refers to a symbolic link the link is renamed; if
+refers to a symbolic link, the link is renamed; if
 .I newpath
-refers to a symbolic link the link will be overwritten.
+refers to a symbolic link, the link will be overwritten.
 .SH RETURN VALUE
 On success, zero is returned.
 On error, \-1 is returned, and
@@ -233,7 +233,7 @@ even if the same filesystem is mounted on both.)
 4.3BSD, C89, C99, POSIX.1-2001.
 .SH BUGS
 On NFS filesystems, you can not assume that if the operation
-failed the file was not renamed.
+failed, the file was not renamed.
 If the server does the rename operation
 and then crashes, the retransmitted RPC which will be processed when the
 server is up again causes a failure.