docs,man: Avoid some ambiguous uses of "may not"

Like much English text, the systemd documentation uses "may not" in the
sense of both "will possibly not" and "is forbidden to".  In many cases
this is OK because the context makes it clear, but in others I felt it
was possible to read the "is forbidden to" sense by mistake: in
particular, I tripped over "the target file may not exist" in
systemd.unit(5) before realizing the correct interpretation.

Use "might not" or "may choose not to" in these cases to make it clear
which sense we mean.

docs/ENVIRONMENT.md

@@ -341,7 +341,7 @@ All tools:
   for cases where we don't need to track given unit type, e.g. `--user` manager
   often doesn't need to deal with device or swap units because they are
   handled by the `--system` manager (PID 1). Note that setting certain unit
-  type as unsupported may not prevent loading some units of that type if they
+  type as unsupported might not prevent loading some units of that type if they
   are referenced by other units of another supported type.
 
 * `$SYSTEMD_DEFAULT_MOUNT_RATE_LIMIT_BURST` — can be set to override the mount

man/homectl.xml

@@ -434,7 +434,7 @@
         denotes 2048-bit RSA with PKCS#1.5 padding and SHA-256. <literal>eddsa</literal> denotes
         EDDSA over Curve25519 with SHA-512.</para>
 
-        <para>Note that your authenticator may not support some algorithms.</para>
+        <para>Note that your authenticator may choose not to support some algorithms.</para>
 
         <xi:include href="version-info.xml" xpointer="v251"/></listitem>
       </varlistentry>

man/integritytab.xml

@@ -80,7 +80,7 @@
         <listitem><para>
         Enable journaled, bitmapped or direct (passthrough) mode. Journaled mode is the default when this option is not specified.
         It provides safety against crashes, but can be slow because all data has to be written twice.
-        Bitmap mode is more efficient since it requires only a single write, but it is less reliable because if data corruption happens when the machine crashes, it may not be detected.
+        Bitmap mode is more efficient since it requires only a single write, but it is less reliable because if data corruption happens when the machine crashes, it might not be detected.
         Direct mode disables the journal and the bitmap. Corresponds to the "direct writes" mode documented in
         <ulink url="https://docs.kernel.org/admin-guide/device-mapper/dm-integrity.html">the dm-integrity documentation</ulink>.
         Note that without a journal, if there is a crash, it is possible that the integrity tags and data will not match. If used, the journal-*

man/sd_bus_set_address.xml

@@ -101,7 +101,7 @@
     If specified, the identifier returned by the peer after the connection is established will be checked and
     the connection will be rejected in case of a mismatch.</para>
 
-    <para>Note that the addresses passed to <function>sd_bus_set_address()</function> may not be verified
+    <para>Note that the addresses passed to <function>sd_bus_set_address()</function> might not be verified
     immediately. If they are invalid, an error may be returned e.g. from a subsequent call to
     <citerefentry><refentrytitle>sd_bus_start</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
     </para>

man/systemctl.xml

@@ -350,7 +350,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err
             "fragment" and "drop-ins" (source files) of units. Each
             file is preceded by a comment which includes the file
             name. Note that this shows the contents of the backing files
-            on disk, which may not match the system manager's
+            on disk, which might not match the system manager's
             understanding of these units if any unit files were
             updated on disk and the <command>daemon-reload</command>
             command wasn't issued since.</para>

man/systemd-cryptenroll.xml

@@ -370,7 +370,7 @@
         denotes 2048-bit RSA with PKCS#1.5 padding and SHA-256. <literal>eddsa</literal> denotes
         EDDSA over Curve25519 with SHA-512.</para>
 
-        <para>Note that your authenticator may not support some algorithms.</para>
+        <para>Note that your authenticator may choose not to support some algorithms.</para>
 
         <xi:include href="version-info.xml" xpointer="v251"/></listitem>
       </varlistentry>

man/systemd.network.xml

@@ -2795,7 +2795,7 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
           prefix length after <literal>/</literal>. DHCP offers from servers in the list are rejected.
           Note that if <varname>AllowList=</varname> is configured then <varname>DenyList=</varname> is
           ignored.</para>
-          <para>Note that this filters only DHCP offers, so the filtering may not work when
+          <para>Note that this filters only DHCP offers, so the filtering might not work when
           <varname>RapidCommit=</varname> is enabled. See also <varname>RapidCommit=</varname> in the above.
           </para>
 
@@ -2809,7 +2809,7 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
           <para>A whitespace-separated list of IPv4 addresses. Each address can optionally take a
           prefix length after <literal>/</literal>. DHCP offers from servers in the list are accepted.
           </para>
-          <para>Note that this filters only DHCP offers, so the filtering may not work when
+          <para>Note that this filters only DHCP offers, so the filtering might not work when
           <varname>RapidCommit=</varname> is enabled. See also <varname>RapidCommit=</varname> in the above.
           </para>
 

man/systemd.unit.xml

@@ -164,7 +164,7 @@
     instance (if any) is always uniquely defined for a given unit and all its aliases. The target of alias
     symlink must point to a valid unit file location, i.e. the symlink target name must match the symlink
     source name as described, and the destination path must be in one of the unit search paths, see UNIT FILE
-    LOAD PATH section below for more details. Note that the target file may not exist, i.e. the symlink may
+    LOAD PATH section below for more details. Note that the target file might not exist, i.e. the symlink may
     be dangling.</para>
 
     <para>Unit files may specify aliases through the <varname>Alias=</varname> directive in the [Install]
@@ -196,7 +196,7 @@
     <filename>.wants/</filename> or <filename>.requires/</filename> must thus point to a valid unit file
     location, i.e. the symlink target name must satisfy the described requirements, and the destination path
     must be in one of the unit search paths, see UNIT FILE LOAD PATH section below for more details. Note
-    that the target file may not exist, i.e. the symlink may be dangling.</para>
+    that the target file might not exist, i.e. the symlink may be dangling.</para>
 
     <para>Along with a unit file <filename>foo.service</filename>, a "drop-in" directory
     <filename>foo.service.d/</filename> may exist. All files with the suffix