[gnome-remote-desktop] settings: Unify code style in gsettings schema

[Jonas Ådahl <jadahl src gnome org>]

commit f74118e926140eb0b86559a9d97fabd6087a9d9a
Author: Pascal Nowack <Pascal Nowack gmx de>
Date:   Tue Nov 23 10:41:46 2021 +0100

    settings: Unify code style in gsettings schema
    
    Like the screencast and remote-desktop API, the code style in the
    gsettings schema is mixed.
    Fix this by replacing all tabulators with spaces.

 src/org.gnome.desktop.remote-desktop.gschema.xml.in | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
---
diff --git a/src/org.gnome.desktop.remote-desktop.gschema.xml.in 
b/src/org.gnome.desktop.remote-desktop.gschema.xml.in
index 7633e000..0779c8c6 100644
--- a/src/org.gnome.desktop.remote-desktop.gschema.xml.in
+++ b/src/org.gnome.desktop.remote-desktop.gschema.xml.in
@@ -32,21 +32,21 @@
       <default>true</default>
       <summary>Only allow remote connections to view the screen content</summary>
       <description>
-       When view-only is true, remote VNC connections cannot manipulate input
-       devices (e.g. mouse and keyboard).
+        When view-only is true, remote VNC connections cannot manipulate input
+        devices (e.g. mouse and keyboard).
       </description>
     </key>
     <key name='auth-method' enum='org.gnome.desktop.remote-desktop.GrdVncAuthMethod'>
       <default>'prompt'</default>
       <summary>Method used to authenticate VNC connections</summary>
       <description>
-       The VNC authentication method describes how a remote connection is
-       authenticated. It can currently be done in two different ways:
+        The VNC authentication method describes how a remote connection is
+        authenticated. It can currently be done in two different ways:
 
-        * prompt   - by prompting the user for each new connection, requiring a
-                     person with physical access to the workstation to
-                     explicitly approve the new connection.
-        * password - by requiring the remote client to provide a known password
+         * prompt   - by prompting the user for each new connection, requiring a
+                      person with physical access to the workstation to
+                      explicitly approve the new connection.
+         * password - by requiring the remote client to provide a known password
       </description>
     </key>
   </schema>