minor restructuring following on from previous commit

flatpak · Jan 13, 2017 · 3c13ba9 · 3c13ba9
1 parent 7bc762c
commit 3c13ba9
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 6 deletions.
diff --git a/docs/elements-of-a-flatpak-app.rst b/docs/elements-of-a-flatpak-app.rst
@@ -26,7 +26,7 @@ When an application is built using flatpak, it is outputted with the following s
 All the files in the export directory must have the application ID as a prefix. This guarantees that applications cannot cause conflicts, and that they can’t override any system installed applications.
 
 Metadata files
-^^^^^^^^^^^^^^
+--------------
 
 The application's ``metadata`` file provides information that allows flatpak to set up the sandbox for running the application. A typical metadata file looks like this::
 

diff --git a/docs/extensions.rst b/docs/extensions.rst
@@ -3,21 +3,18 @@ Extensions
 
 In the introduction, Flatpak's key concepts were introduced: runtimes, bundled applications, SDKs, and sandboxes. There is one other concept that must be added to this list: extensions.
 
-An extension is an optional piece that can be plugged into a filesystem, and they can be created for both applications and runtimes. Extensions are used for several purposes in Flatpak:
+An extension is an optional piece that can be plugged into a filesystem. They can be created for both applications and runtimes and are used for several purposes:
 
 * To separate translations and debug information from each application. Since these parts can be large and are not always wanted, it makes sense to allow them to be optionally installed alongside the application.
 * For software components that need to be distributed separately from an application or library. Primary examples of this include GL libraries (which need to be provided by the host) and GStreamer plugins (which can't always be distributed for legal reasons).
 
-metadata
---------
-
 Like runtimes, extensions are declared in the metadata of an application. They are then mounted by flatpak inside the application's sandbox. A typical extension section in a metadata file looks like this::
 
   [Extension org.gnome.Platform.GL]
   version=1.4
   directory=lib/GL
 
-More complicated extension points can accept multiple extensions that are mounted below a single directory. For example, in this example the ``org.freedesktop.Platform`` runtime defines an extension point for GStreamer::
+More complicated extension points can accept multiple extensions that are mounted below a single directory. For example, the ``org.freedesktop.Platform`` runtime defines an extension point for GStreamer::
 
   [Extension org.freedesktop.Platform.GStreamer]
   version=1.4