doc: remove double white space

Pick-to: 6.6
Change-Id: I68b835bb5fa00d35fe5406deee2acc83c7bac7cb
Reviewed-by: Adrian Herrmann <[email protected]>

Author: cmaureir

README.md

@@ -61,19 +61,19 @@ are found by the QtNetwork module.
 ## Building Additional Options
 
 On Linux and macOS you can use the option `--standalone` to embed Qt libraries
-into the PySide6 package.  The option does not affect Windows, because it is
+into the PySide6 package. The option does not affect Windows, because it is
 used implicitly, i.e. all relevant DLLs have to be copied into the PySide6
 package anyway, because there is no proper rpath support on the platform.
 
 You can use the option `--rpath=/path/to/lib/path` to specify which rpath
-values should be embedded into the PySide6 modules and shared libraries.  This
+values should be embedded into the PySide6 modules and shared libraries. This
 overrides the automatically generated values when the option is not specified.
 
 You can use the option `--qt-conf-prefix` to pass a path relative to the
 PySide6 installed package, which will be embedded into an auto-generated
-`qt.conf` registered in the Qt resource system.  This path will serve as the
+`qt.conf` registered in the Qt resource system. This path will serve as the
 PrefixPath for QLibraryInfo, thus allowing to choose where Qt plugins should be
-loaded from.  This option overrides the usual prefix chosen by `--standalone`
+loaded from. This option overrides the usual prefix chosen by `--standalone`
 option, or when building on Windows.
 
 To temporarily disable registration of the internal `qt.conf` file, a new
@@ -209,7 +209,7 @@ make sure to specify the following things:
    a system interpreter, or a virtualenv one for example)
 
 Once that is done, just re-run CMake, so that it picks up the new environment
-values.  If needed, all other cache variables defined by the project files can
+values. If needed, all other cache variables defined by the project files can
 be re-adjusted (for example FORCE_LIMITED_API).
 
 ## Command line CMake case

README.pyside6.md

@@ -89,6 +89,6 @@ and [join our community](https://wiki.qt.io/Qt_for_Python#Community)!
 ### Licensing
 
 PySide6 is available under both Open Source (LGPLv3/GPLv2) and commercial
-license.  Using PyPi is the recommended installation source, because the
-content of the wheels is valid for both cases.  For more information, refer to
+license. Using PyPi is the recommended installation source, because the
+content of the wheels is valid for both cases. For more information, refer to
 the [Qt Licensing page](https://www.qt.io/licensing/).

README.pyside6_addons.md

@@ -60,6 +60,6 @@ and [join our community](https://wiki.qt.io/Qt_for_Python#Community)!
 ### Licensing
 
 PySide6 is available under both Open Source (LGPLv3/GPLv2) and commercial
-license.  Using PyPi is the recommended installation source, because the
-content of the wheels is valid for both cases.  For more information, refer to
+license. Using PyPi is the recommended installation source, because the
+content of the wheels is valid for both cases. For more information, refer to
 the [Qt Licensing page](https://www.qt.io/licensing/).

README.pyside6_essentials.md

@@ -51,6 +51,6 @@ and [join our community](https://wiki.qt.io/Qt_for_Python#Community)!
 ### Licensing
 
 PySide6 is available under both Open Source (LGPLv3/GPLv2) and commercial
-license.  Using PyPi is the recommended installation source, because the
-content of the wheels is valid for both cases.  For more information, refer to
+license. Using PyPi is the recommended installation source, because the
+content of the wheels is valid for both cases. For more information, refer to
 the [Qt Licensing page](https://www.qt.io/licensing/).

README.shiboken6-generator.md

@@ -1,6 +1,6 @@
 # Shiboken6-generator
 
-Shiboken is the generator used by the Qt for Python project.  It outputs C++
+Shiboken is the generator used by the Qt for Python project. It outputs C++
 code for CPython extensions, which can be compiled and transformed into
 a Python module.
 

examples/qml/editingmodel/doc/editingmodel.rst

@@ -2,7 +2,7 @@ QAbstractListModel in QML
 =========================
 
 This example shows how to add, remove and move items inside a QML
-ListView, but showing and editing the data via roles using  a
+ListView, but showing and editing the data via roles using a
 QAbstractListModel from Python.
 
 You can add new elements and reset the view using the two top buttons,

examples/qml/tutorials/extending-qml-advanced/adding/doc/adding.rst

@@ -18,12 +18,12 @@ The ``Person`` type can be used from QML like this:
 Declare the Person Class
 ------------------------
 
-All QML types map to C++ types.  Here we declare a basic C++ Person class
+All QML types map to C++ types. Here we declare a basic C++ Person class
 with the two properties we want accessible on the QML type - name and shoeSize.
 Although in this example we use the same name for the C++ class as the QML
 type, the C++ class can be named differently, or appear in a namespace.
 
-The Person class implementation is quite basic.  The property accessors simply
+The Person class implementation is quite basic. The property accessors simply
 return members of the object instance.
 
 .. code-block:: python

examples/qml/tutorials/extending-qml-advanced/properties/doc/properties.rst

@@ -75,10 +75,10 @@ The class contains a member to store the celebrant object, and also a
 list member storing the Person instances.
 
 In QML, the type of a list properties - and the guests property is a list of
-people - are all of type ListProperty.  ListProperty is simple value
-type that contains a set of functions.  QML calls these functions
+people - are all of type ListProperty. ListProperty is simple value
+type that contains a set of functions. QML calls these functions
 whenever it needs to read from, write to or otherwise interact with
-the list.  In addition to concrete lists like the people list used in this
+the list. In addition to concrete lists like the people list used in this
 example, the use of QQmlListProperty allows for "virtual lists" and other advanced
 scenarios.
 

sources/pyside6/doc/commercial/index.rst

@@ -16,7 +16,7 @@ any of the following licenses:
 #. Qt for Device Creation Enterprise (DCE)
 
 The only difference is that the ADP license **does not** include the extra
-``Qt OPC UA``,  ``Qt MQTT`` and ``Qt CoAP`` modules, which are distributed in
+``Qt OPC UA``, ``Qt MQTT`` and ``Qt CoAP`` modules, which are distributed in
 a special Python wheel.
 
 All commercial licenses include the 5.15.x and 6.2.x LTS releases.
@@ -93,7 +93,7 @@ Maintenance Tool
 ^^^^^^^^^^^^^^^^
 
 As a commercial user, you are able to download the commercial set of wheels
-from the `Qt Maintenance Tool`_.  The same versions that are available for
+from the `Qt Maintenance Tool`_. The same versions that are available for
 Qt/C++ are available for the Python bindings.
 
 The wheels will be downloaded, but not installed, mainly because they should

sources/pyside6/doc/deployment/deployment-pyside6-deploy.rst

@@ -4,7 +4,7 @@ pyside6-deploy: the deployment tool for Qt for Python
 #####################################################
 
 ``pyside6-deploy`` is an easy to use tool for deploying PySide6 applications to different
-platforms.  It is a  wrapper around `Nuitka <https://nuitka.net/>`_, a Python compiler that
+platforms. It is a wrapper around `Nuitka <https://nuitka.net/>`_, a Python compiler that
 compiles your Python code to C code, and links with libpython to produce the final executable.
 
 The final executable produced has a ``.exe`` suffix on Windows. For Linux and macOS, they have a

sources/pyside6/doc/extras/QtUiTools.rst

@@ -1,5 +1,5 @@
 Qt Designer forms are processed at run-time to produce
-dynamically-generated user interfaces.  In order to generate a form at
+dynamically-generated user interfaces. In order to generate a form at
 run-time, a resource file containing a UI file is needed.
 
 A form loader object, provided by the ``QUiLoader`` class, is used to

sources/pyside6/doc/faq/whatisqt.rst

@@ -25,7 +25,7 @@ As a framework, Qt has many components, which are distributed by components
 and modules, for example, `qtbase <https://code.qt.io/cgit/qt/qtbase.git/>`_
 is the base component that holds many modules, like: ``QtCore``, ``QtGui``,
 ``QtWidgets``, ``QtNetwork``, etc.
-All those  modules contains many classes that you can directly use, like the
+All those modules contains many classes that you can directly use, like the
 case of the `Classes of QtCore <https://doc.qt.io/qt-6/qtcore-module.html>`_
 from which you can find classes like ``QFile``, ``QTime``, ``QByteArray``, etc.
 

sources/pyside6/doc/gettingstarted/index.rst

@@ -143,7 +143,7 @@ Cross Compilation
 -----------------
 
 Starting from 6.3, it is possible to cross-compile Shiboken (module), and
-PySide.  This functionality is still in Technical Preview, which means it could
+PySide. This functionality is still in Technical Preview, which means it could
 change in the future releases.
 
 .. important:: The only supported configuration is using a host Linux
@@ -177,7 +177,7 @@ Prerequisites
 ~~~~~~~~~~~~~
 
 First and foremost, you need to have access to the target device because you
-need to copy several system files (sysroot).  We recommend a Linux OS that has
+need to copy several system files (sysroot). We recommend a Linux OS that has
 the latest Qt versions, like `Manjaro ARM`_ or `Archlinux ARM`_.
 
 * (target) Install Qt 6.3+ on the system using the package manager.
@@ -190,7 +190,7 @@ the latest Qt versions, like `Manjaro ARM`_ or `Archlinux ARM`_.
 
 After installing these prerequisites, copy the ``target`` sysroot to your
 ``host`` computer. This process is tricky, because copying system files from
-another computer might cause problems with the symbolic links.  Here you
+another computer might cause problems with the symbolic links. Here you
 have two options to achieve that.
 
 Option A: Copying the files
@@ -275,7 +275,7 @@ and unpacked it.
 
 With those compilers, now you need a CMake toolchain file. This is
 a configuration file to set the compilers and sysroot information, together
-with extra options like compilation flags, and other details.  You can use the
+with extra options like compilation flags, and other details. You can use the
 following file as an example, but keep in mind they might vary:
 
 .. code-block:: cmake

sources/pyside6/doc/modules.rst

@@ -82,7 +82,7 @@ Qt Modules Supported by Qt for Python
 
     .. grid-item-card:: :mod:`QtOpenGL Widgets <PySide6.QtOpenGLWidgets>`
 
-        Provides the  OpenGLWidget class enabling OpenGL rendering for
+        Provides the OpenGLWidget class enabling OpenGL rendering for
         a certain part of the widget tree.
 
     .. grid-item-card:: :mod:`Qt Positioning <PySide6.QtPositioning>`

sources/pyside6/doc/tutorials/basictutorial/signals_and_slots.rst

@@ -57,7 +57,7 @@ could be implemented by placing a ``QToolButton`` to the right of the
     button.clicked.connect(line_edit.clear)
 
 ``connect()`` returns a ``QMetaObject.Connection`` object, which can be
-used  with the ``disconnect()`` method to sever the connection.
+used with the ``disconnect()`` method to sever the connection.
 
 Signals can also be connected to free functions:
 

sources/pyside6/doc/tutorials/basictutorial/translations.rst

@@ -172,7 +172,7 @@ is first created:
     xgettext -L Python -o locales/example.pot main.py
 
 This file has a few generic placeholders which can be replaced by the
-appropriate values.  It is then copied to the ``de_DE/LC_MESSAGES`` directory.
+appropriate values. It is then copied to the ``de_DE/LC_MESSAGES`` directory.
 
 .. code-block:: bash
 

sources/pyside6/doc/tutorials/basictutorial/uifiles.rst

@@ -213,7 +213,7 @@ Custom Widgets in Qt Designer
 in the widget box and can be dragged onto the form just like Qt's widgets (see
 `Using Custom Widgets with Qt Designer <https://doc.qt.io/qt-6/designer-using-custom-widgets.html>`_
 ). Normally, this requires implementing the widget as a plugin to Qt Designer
-written in  C++ implementing its
+written in C++ implementing its
 `QDesignerCustomWidgetInterface <https://doc.qt.io/qt-6/qdesignercustomwidgetinterface.html>`_ .
 
 Qt for Python provides a simple interface for this which is similar to
@@ -225,7 +225,7 @@ the taskmenuextension example (file ``tictactoe.py``).
 
 Registering this with Qt Designer is done by providing
 a registration script named ``register*.py`` and pointing
-the  path-type environment variable ``PYSIDE_DESIGNER_PLUGINS``
+the path-type environment variable ``PYSIDE_DESIGNER_PLUGINS``
 to the directory.
 
 The code of the registration script looks as follows:

sources/pyside6/doc/tutorials/expenses/expenses.rst

@@ -56,7 +56,7 @@ Now that our class is defined, create an instance of it and call `show()`.
 Menu bar
 --------
 
-Using a `QMainWindow` gives some features for free, among them a *menu bar*.  To use it, you need
+Using a `QMainWindow` gives some features for free, among them a *menu bar*. To use it, you need
 to call the method `menuBar()` and populate it inside the `MainWindow` class.
 
 .. literalinclude:: steps/02-expenses.py
@@ -94,7 +94,7 @@ Window layout
 Now that the main empty window is in place, you need to start adding widgets to achieve the main
 goal of creating an expenses application.
 
-After declaring the example data, you can visualize it on a simple `QTableWidget`.  To do so, you
+After declaring the example data, you can visualize it on a simple `QTableWidget`. To do so, you
 will add this procedure to the `Widget` constructor.
 
 .. warning:: Only for the example purpose a QTableWidget will be used,

sources/pyside6/doc/tutorials/portingguide/index.rst

@@ -63,7 +63,7 @@ C++ vs Python
       doStuff(key, value)
 
 In this example, ``func()`` would treat ``var`` as a local
-name without the ``global`` statement.  This would lead to
+name without the ``global`` statement. This would lead to
 a ``NameError`` in the ``value is None`` handling, on
 accessing ``var``. For more information about this, see
 `Python refernce documentation <python refdoc>`_.

sources/pyside6/doc/tutorials/qmlintegration/qmlintegration.rst

@@ -2,17 +2,17 @@ Python-QML integration
 ======================
 
 This tutorial provides a quick walk-through of a python application that loads, and interacts with
-a QML file.  QML is a declarative language that lets you design UIs faster than a traditional
-language, such as C++.  The QtQml and QtQuick modules provides the necessary infrastructure for
+a QML file. QML is a declarative language that lets you design UIs faster than a traditional
+language, such as C++. The QtQml and QtQuick modules provides the necessary infrastructure for
 QML-based UIs.
 
 In this tutorial, you will learn how to integrate Python with a QML application.
 This mechanism will help us to understand how to use Python as a backend for certain
-signals from the UI elements in the QML interface.  Additionally, you will learn how to provide
+signals from the UI elements in the QML interface. Additionally, you will learn how to provide
 a modern look to your QML application using one of the features from Qt Quick Controls 2.
 
 The tutorial is based on an application that allow you to set many text properties, like increasing
-the font size, changing the color, changing the style, and so on.  Before you begin, install the
+the font size, changing the color, changing the style, and so on. Before you begin, install the
 `PySide6 <https://pypi.org/project/PySide6/>`_ Python packages.
 
 The following step-by-step process will guide you through the key elements of the QML based
@@ -68,7 +68,7 @@ application and PySide6 integration:
 
    The properties *Italic*, *Bold*, and *Underline* are mutually
    exclusive, this means only one can be active at any time.
-   To achieve  this each time we select one of these options, we
+   To achieve this each time we select one of these options, we
    check the three properties via the QML element property as you can
    see in the above snippet.
    Only one of the three will return *True*, while the other two

sources/pyside6/doc/videos.rst

@@ -37,7 +37,7 @@ Tutorials
         :img-top: https://img.youtube.com/vi/i-utZN_NP6c/mqdefault.jpg
         :link: https://www.youtube.com/embed/i-utZN_NP6c
 
-        How  to install PySide6 on a new virtual environment
+        How to install PySide6 on a new virtual environment
 
 
 Community events

sources/shiboken6/doc/gettingstarted.rst

@@ -40,7 +40,7 @@ The same can be used for the module, changing the value of ``internal-build-type
 ``shiboken6-module``.
 
 .. warning:: If you are planning to use PySide too, for examples like
-    'scriptableapplication' you need to have build it as well.  The main issue is
+    'scriptableapplication' you need to have build it as well. The main issue is
     that your PySide and Shiboken needs to be build using the same dependencies
     from Qt and libclang.
 

sources/shiboken6/doc/typesystem_manipulating_objects.rst

@@ -136,7 +136,7 @@ language API (both are set to true by default).
 The ``remove`` attribute is an *optional* boolean attribute, which can
 mark the field to be discarded on generation.
 
-The  *optional* ``rename`` attribute can be used to change the name of the
+The *optional* ``rename`` attribute can be used to change the name of the
 given field in the generated target language API.
 
 The *optional* ``opaque-container`` attribute specifies whether
@@ -183,7 +183,7 @@ The ``since`` attribute specify the API version when this function was modified.
 The ``allow-thread`` attribute specifies whether a function should be wrapped
 into ``Py_BEGIN_ALLOW_THREADS`` and ``Py_END_ALLOW_THREADS``, that is,
 temporarily release the GIL (global interpreter lock). Doing so is required
-for any thread-related  function (wait operations), functions that might call
+for any thread-related function (wait operations), functions that might call
 a virtual function (potentially reimplemented in Python), and recommended for
 lengthy I/O operations or similar. It has performance costs, though.
 The value ``auto`` means that it will be turned off for functions for which
@@ -249,10 +249,10 @@ and disables generating the code for overriding the function in Python
 The ``remove`` attribute is an *optional* boolean attribute, which can
 mark the function to be discarded on generation.
 
-The  *optional* ``rename`` attribute can be used to change the name of the
+The *optional* ``rename`` attribute can be used to change the name of the
 given function in the generated target language API.
 
-The  *optional* ``access`` attribute changes the access privileges of the
+The *optional* ``access`` attribute changes the access privileges of the
 given function in the generated target language API.
 
 The *optional* **snake-case** attribute allows for overriding the value

sources/shiboken6/doc/typesystem_ownership.rst

@@ -87,7 +87,7 @@ If the class has a virtual destructor (and C++ classes with virtual methods shou
 C++ instance invalidates the wrapper only when the overridden destructor is called.
 
 An instance of the **shell** is created when created in Python. However,
-when  the object is created in C++, like in a factory method or a parameter
+when the object is created in C++, like in a factory method or a parameter
 to a virtual function like ``QObject::event(QEvent *)``, the wrapped object
 is a C++ instance of the native class, not the **shell** one, and we cannot
 know when it is destroyed.
@@ -178,8 +178,8 @@ To solve this, you should hold a reference to the source object, like in
    renderer.render()
 
 
-Ownership Management in  the Typesystem
-=======================================
+Ownership Management in the Typesystem
+======================================
 
 Python Wrapper Code
 -------------------