Commit 9eee1ef4 authored by Piotr Drąg's avatar Piotr Drąg 😐
Browse files
parent 59ea0915
......@@ -45,7 +45,7 @@
text editor, you can modify <em>keyfiles</em> found in
<em>keyfile directories</em>. Each keyfile directory corresponds to a
particular system database file, and has the same name as the database file
with a '.d' extension appended (for example,
with a .d extension appended (for example,
<file>/etc/dconf/db/local.d</file>). All keyfile directories are found in
<file its:translate="no">/etc/dconf/db</file>, and each one contains keyfiles
in a special format that can be compiled into the
......
......@@ -29,7 +29,7 @@
<p>On startup, <sys>dconf</sys> consults the DCONF_PROFILE environment
variable. If set, <sys>dconf</sys> attempts to open the named profile and
aborts if that fails. If the environment variable is not set,
<sys>dconf</sys> attempts to open the profile named "user". If that
<sys>dconf</sys> attempts to open the profile named user. If that
fails, it will fall back to an internal hard-wired configuration.</p>
<p>Each line in a profile specifies one <sys>dconf</sys> database. The first
......
......@@ -39,7 +39,7 @@
<p>To give you an idea of the power of <sys>dconf</sys> within GNOME, a
<sys>dconf</sys> key exists for most every setting that a user can click on
in the GNOME desktop or in any GNOME application. In addition to this, there
are some system and application settings that can't even be changed from
are some system and application settings that cant even be changed from
within the user interface, but which <em>can</em> be changed by using
<sys>dconf</sys>.</p>
......
......@@ -51,7 +51,7 @@ enabled-extensions=['<input>myextension1@myname.example.com</input>', '<input>my
</code>
</listing>
<p>The <code>enabled-extensions</code> key specifies the enabled
extensions using the extensions' uuid
extensions using the extensions uuid
(<code>myextension1@myname.example.com</code> and
<code>myextension2@myname.example.com</code>).</p>
</item>
......
......@@ -29,7 +29,7 @@
provide a set of extensions that the user has to use.</p>
<p>Locking down the <code>org.gnome.shell.development-tools</code> key
ensures that the user cannot use GNOME Shell's integrated debugger and
ensures that the user cannot use GNOME Shells integrated debugger and
inspector tool (<app>Looking Glass</app>) to disable any mandatory
extensions.</p>
......@@ -59,14 +59,14 @@ development-tools=false
</code>
</listing>
<p>The <code>enabled-extensions</code> key specifies the enabled
extensions using the extensions' uuid
extensions using the extensions uuid
(<code>myextension1@myname.example.com</code> and
<code>myextension2@myname.example.com</code>).</p>
<p>The <code>development-tools</code> key is set to false to disable
access to Looking Glass.</p>
</item>
<item>
<p>Override the user's setting and prevent the user from changing it in
<p>Override the users setting and prevent the user from changing it in
<file>/etc/dconf/db/local.d/locks/extensions</file>:</p>
<listing>
<code>
......
......@@ -34,7 +34,7 @@
<file>/usr/share/gnome-shell/extensions/&lt;uuid&gt;</file>.</p>
<p>To view installed extensions, you can use <app>Looking Glass</app>, GNOME
Shell's integrated debugger and inspector tool.</p>
Shells integrated debugger and inspector tool.</p>
<steps>
<title>View installed extensions</title>
......
......@@ -42,7 +42,7 @@
prevent the user from installing a new terminal application.</p>
<comment>
<cite>Petr Kovar</cite>
<p>We have yet to cover removing a menu item in this guide. We don't
<p>We have yet to cover removing a menu item in this guide. We dont
want system admins having to modify .desktop files as those could be
overwritten on system update.</p>
</comment>
......@@ -66,7 +66,7 @@
disable-command-line=true</code>
</item>
<item>
<p>Override the user's setting and prevent the user from changing it in
<p>Override the users setting and prevent the user from changing it in
<file>/etc/dconf/db/local.d/locks/lockdown</file>:</p>
<code># List the keys used to configure lockdown
/org/gnome/desktop/lockdown/disable-command-line</code>
......
......@@ -59,7 +59,7 @@
</item>
</steps>
<p>Depending on how the domain is configured, a prompt may show up asking for
the domain administrator's name and password in order to proceed.</p>
the domain administrators name and password in order to proceed.</p>
</section>
<section id="enterprise-login-change-to">
<title>Change to use enterprise credentials to log into GNOME</title>
......@@ -77,7 +77,7 @@
</item>
<item>
<p>Click the <gui>Unlock</gui> button and type the computer
administrator's password.</p>
administrators password.</p>
</item>
<item>
<p>Click the <gui>[+]</gui> button in the lower left of
......@@ -92,7 +92,7 @@
</item>
</steps>
<p>Depending on how your domain is configured, a prompt may show up asking for
the domain administrator's name and password in order to proceed.
the domain administrators name and password in order to proceed.
</p>
</section>
<section id="enterprise-login-troubleshoot">
......
......@@ -44,8 +44,8 @@ application/xhtml+xml=epiphany.desktop</code>
The default application (<app>Epiphany</app>) is defined
by specifying its corresponding <file>.desktop</file> file
(<file>epiphany.desktop</file>). The system default location
for other applications' <file>.desktop</file> files is
<file>/usr/share/applications/</file>. Individual users'
for other applications <file>.desktop</file> files is
<file>/usr/share/applications/</file>. Individual users
<file>.desktop</file> files can be stored in
<file>~/.local/share/applications/</file>.
</p>
......@@ -82,7 +82,7 @@ application/xhtml+xml=<var>myapplication2.desktop</var>;</code>
that the default registered application has been set correctly:
</p>
<screen><output>$ </output><input>gvfs-mime --query text/html</input>
Default application for 'text/html': myapplication1.desktop
Default application for text/html: myapplication1.desktop
Registered applications:
myapplication1.desktop
epiphany.desktop
......
......@@ -45,7 +45,7 @@ application/xhtml+xml=epiphany.desktop</code>
The default application (<app>Epiphany</app>) is
defined by specifying its corresponding <file>.desktop</file>
file (<file>epiphany.desktop</file>). The default location for
other applications' <file>.desktop</file> files is
other applications <file>.desktop</file> files is
<file>/usr/share/applications/</file>.
</p>
</item>
......@@ -80,7 +80,7 @@ application/xhtml+xml=<var>myapplication2.desktop</var>;</code>
that the default registered application has been set correctly:
</p>
<screen><output>$ </output><input>gvfs-mime --query text/html</input>
Default application for 'text/html': myapplication1.desktop
Default application for text/html: myapplication1.desktop
Registered applications:
myapplication1.desktop
epiphany.desktop
......
......@@ -96,7 +96,7 @@ Exec=<var>myapplication1</var></code>
<cmd>gvfs-mime --query</cmd> command:
</p>
<screen><output>$ </output><input>gvfs-mime --query application/x-newtype</input>
Default application for 'application/x-newtype': myapplication1.desktop
Default application for application/x-newtype: myapplication1.desktop
Registered applications:
myapplication1.desktop
Recommended applications:
......
......@@ -97,7 +97,7 @@ Exec=<var>myapplication1</var></code>
<cmd>gvfs-mime --query</cmd> command:
</p>
<screen><output>$ </output><input>gvfs-mime --query application/x-newtype</input>
Default application for 'application/x-newtype': myapplication1.desktop
Default application for application/x-newtype: myapplication1.desktop
Registered applications:
myapplication1.desktop
Recommended applications:
......
......@@ -93,7 +93,7 @@
that GNOME uses to store information about known MIME types.
</p>
<p>
The most important part of the MIME database from the system administrator's
The most important part of the MIME database from the system administrators
point of view is the <file>/usr/share/mime/packages/</file>
directory where the MIME type related files specifying information on
known MIME types are stored. One example of such a file is
......
......@@ -70,7 +70,7 @@
</item>
<item>
<p>
To specify a default session for a user, update the user's
To specify a default session for a user, update the users
<sys>account service</sys> in the
<file>/var/lib/AccountsService/users/<var>username</var>
file</file>:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment