[PATCH] memfd_create.2: fix typos

[PATCH] memfd_create.2: fix typos

[Mike Rapoport]

Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
---
 man2/memfd_create.2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man2/memfd_create.2 b/man2/memfd_create.2
index 15b1362..9be8f3c 100644
--- a/man2/memfd_create.2
+++ b/man2/memfd_create.2
@@ -221,7 +221,7 @@ used with the file-sealing APIs provided by
 .PP
 The
 .BR memfd_create ()
-system call also has uses without file sealing
+system call also have uses without file sealing
 (which is why file-sealing is disabled, unless explicitly requested with the
 .BR MFD_ALLOW_SEALING
 flag).
@@ -254,7 +254,7 @@ signal.)
 Dealing with untrusted peers imposes extra complexity on
 code that employs shared memory.
 Memory sealing enables that extra complexity to be eliminated,
-by allowing a process to operate secure in the knowledge that
+by allowing a process to operate securely in the knowledge that
 its peer can't modify the shared memory in an undesired fashion.
 .PP
 An example of the usage of the sealing mechanism is as follows:
-- 
2.7.4

Re: [PATCH] memfd_create.2: fix typos

[Mike Rapoport]

On Wed, Oct 30, 2019 at 11:39:18PM +0100, Mike Rapoport wrote:
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
>  man2/memfd_create.2 | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/man2/memfd_create.2 b/man2/memfd_create.2
> index 15b1362..9be8f3c 100644
> --- a/man2/memfd_create.2
> +++ b/man2/memfd_create.2
> @@ -221,7 +221,7 @@ used with the file-sealing APIs provided by
>  .PP
>  The
>  .BR memfd_create ()
> -system call also has uses without file sealing
> +system call also have uses without file sealing

Oops, somehow I've misread it as "can has uses" :(

>  (which is why file-sealing is disabled, unless explicitly requested with the
>  .BR MFD_ALLOW_SEALING
>  flag).
> @@ -254,7 +254,7 @@ signal.)
>  Dealing with untrusted peers imposes extra complexity on
>  code that employs shared memory.
>  Memory sealing enables that extra complexity to be eliminated,
> -by allowing a process to operate secure in the knowledge that
> +by allowing a process to operate securely in the knowledge that
>  its peer can't modify the shared memory in an undesired fashion.
>  .PP
>  An example of the usage of the sealing mechanism is as follows:
> -- 
> 2.7.4
> 

-- 
Sincerely yours,
Mike.