Use "bitwise OR" instead of "bitwise-or" (with fonts).
No other pages spell it like this.
Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
.BR ntp_adjtime ()
are equivalent but differently named.)
It is a bit mask containing a
-.RI bitwise- or
+bitwise OR
combination of zero or more of the following bits:
.TP
.B ADJ_OFFSET
.PP
The
.I flags
-mask is specified as a bitwise-OR of zero or more of
+mask is specified as a bitwise OR of zero or more of
the constants listed below.
Except as noted below, these flags are available
(and have the same effect) in both
.I prot
is a combination of the following access flags:
.B PROT_NONE
-or a bitwise-or of the other values in the following list:
+or a bitwise OR of the other values in the following list:
.TP
.B PROT_NONE
The memory cannot be accessed at all.
.PP
In addition, zero or more file creation flags and file status flags
can be
-.RI bitwise- or 'd
+bitwise ORed
in
.IR flags .
The
In order to indicate that a system call is called under the x32 ABI,
an additional bit,
.BR __X32_SYSCALL_BIT ,
-is bitwise-ORed with the system call number.
+is bitwise ORed with the system call number.
The ABI used by a process affects some process behaviors,
including signal handling or system call restarting.
.IP \[bu]
.PP
.I cflags
is the
-.RB bitwise- or
+bitwise OR
of zero or more of the following:
.TP
.B REG_EXTENDED
are used to provide information regarding the location of any matches.
.I eflags
is the
-.RB bitwise- or
+bitwise OR
of zero or more of the following flags:
.TP
.B REG_NOTBOL