one more fix

Author: gewarren

xml/System.Threading/Semaphore.xml

@@ -444,7 +444,7 @@ Because named semaphores are visible throughout the operating system, they can b
 
 If you want to find out whether a named system semaphore exists, use the <xref:System.Threading.Semaphore.OpenExisting%2A> method. The <xref:System.Threading.Semaphore.OpenExisting%2A> method attempts to open an existing named semaphore, and throws an exception if the system semaphore does not exist.
 
-On Windows, `options` can be provided to specify whether the named semaphore is accessible to the current user only or to all users. It also allows to specify whether the named semaphore is accessible to processes in the current session only or to all sessions. For more information, see <xref:System.Threading.NamedWaitHandleOptions>.
+On Windows, `options` can be provided to specify whether the named semaphore is accessible to the current user only or to all users. It also allows you to specify whether the named semaphore is accessible to processes in the current session only or to all sessions. For more information, see <xref:System.Threading.NamedWaitHandleOptions>.
 
 > [!CAUTION]
 > On Unix-based operating systems, the `options` parameter has no effect as named semaphores are not supported.
@@ -621,7 +621,7 @@ If you specify `null` or an empty string for `name`, a local semaphore is create
 
 Because named semaphores are visible throughout the operating system, they can be used to coordinate resource use across process boundaries.
 
-On Windows, `options` can be provided to specify whether the named semaphore is accessible to the current user only or to all users. It also allows to specify whether the named semaphore is accessible to processes in the current session only or to all sessions. For more information, see <xref:System.Threading.NamedWaitHandleOptions>.
+On Windows, `options` can be provided to specify whether the named semaphore is accessible to the current user only or to all users. It also allows you to specify whether the named semaphore is accessible to processes in the current session only or to all sessions. For more information, see <xref:System.Threading.NamedWaitHandleOptions>.
 
 > [!CAUTION]
 > On Unix-based operating systems, the `options` parameter has no effect as named semaphores are not supported.