Fix NumPy capitalization

Author: Starbuck5

docs/reST/ref/image.rst

@@ -245,7 +245,7 @@ following formats.
 
    .. note:: The use of this function is recommended over :func:`tostring` as of pygame 2.1.3.
              This function was introduced so it matches nicely with other
-             libraries (PIL, numpy, etc), and with people's expectations.
+             libraries (PIL, NumPy, etc), and with people's expectations.
 
    .. versionadded:: 2.1.3
    .. versionchanged:: 2.2.0 Now supports keyword arguments.
@@ -290,7 +290,7 @@ following formats.
 
    .. note:: The use of this function is recommended over :func:`fromstring` as of pygame 2.1.3.
              This function was introduced so it matches nicely with other
-             libraries (PIL, numpy, etc), and with people's expectations.
+             libraries (PIL, NumPy, etc), and with people's expectations.
 
    .. versionadded:: 2.1.3
    .. versionadded:: 2.1.4 Added a 'pitch' argument and support for keyword arguments.

docs/reST/ref/mixer.rst

@@ -364,7 +364,7 @@ The following file formats are supported
    it and the Sound object.
 
    For now buffer and array support is consistent with ``sndarray.make_sound``
-   for Numeric arrays, in that sample sign and byte order are ignored. This
+   for NumPy arrays, in that sample sign and byte order are ignored. This
    will change, either by correctly handling sign and byte order, or by raising
    an exception when different. Also, source samples are truncated to fit the
    audio sample size. This will not change.

docs/reST/ref/surfarray.rst

@@ -30,7 +30,7 @@ specific pixel value of a color. Integer pixel values can only be used directly
 between surfaces with matching pixel layouts (see :class:`pygame.Surface`).
 
 All functions that refer to "array" will copy the surface information to a new
-numpy array. All functions that refer to "pixels" will directly reference the
+NumPy array. All functions that refer to "pixels" will directly reference the
 pixels from the surface and any changes performed to the array will make changes
 in the surface. As this last functions share memory with the surface, this one
 will be locked during the lifetime of the array.