fix typo in scipy.fft docs
@@ -31,7 +31,7 @@ Code compatibility features
---------------------------
1. The boolean switch ``cupy.fft.config.enable_nd_planning`` also affects the FFT functions in this module, see :doc:`./fft`. Moreover, as with other FFT modules in CuPy, FFT functions in this module can take advantage of an existing cuFFT plan (returned by :func:`cupyx.scipy.fftpack.get_fft_plan`) when used as a context manager.
-2. Like in ``scipy.fft``, all FFT functions in this module have an optional argument ``overwrite_x`` (default is ``False``), which has the same semantics as in ``scipy.fft``: when it is set to ``True``, the input array ``x`` *can* (not *will*) be overwritten arbitrary. This is not an in-place FFT, the user should always use the return value from the functions, e.g. ``x = cupyx.scipy.fft.fft(x, ..., overwrite_x=True, ...)``.
+2. Like in ``scipy.fft``, all FFT functions in this module have an optional argument ``overwrite_x`` (default is ``False``), which has the same semantics as in ``scipy.fft``: when it is set to ``True``, the input array ``x`` *can* (not *will*) be overwritten arbitrarily. This is not an in-place FFT, the user should always use the return value from the functions, e.g. ``x = cupyx.scipy.fft.fft(x, ..., overwrite_x=True, ...)``.
3. The ``cupyx.scipy.fft`` module can also be used as a backend for ``scipy.fft`` e.g. by installing with ``scipy.fft.set_backend(cupyx.scipy.fft)``. This can allow ``scipy.fft`` to work with both ``numpy`` and ``cupy`` arrays.
