Merge pull request #144 from guillermooo/edit-projectrs

English?
guillermooo · Apr 5, 2015 · a29eede · a29eede
2 parents 6bccbcf + d19b418
commit a29eede
Show file tree

Hide file tree

Showing 8 changed files with 11 additions and 11 deletions.
diff --git a/source/extensibility/syntaxdefs.rst b/source/extensibility/syntaxdefs.rst
@@ -175,7 +175,7 @@ Let's examine the key elements.
     programming language you are creating the syntax definition for.
 
 ``scopeName``
-    The top level scope for this syntax definition. It takes the form
+    The topmost scope for this syntax definition. It takes the form
     ``source.<lang_name>`` or ``text.<lang_name>``. For programming languages,
     use ``source``. For markup and everything else, use ``text``.
 

diff --git a/source/file_management/file_management.rst b/source/file_management/file_management.rst
@@ -216,7 +216,7 @@ The ``.sublime-project`` Format
 -------------------------------
 
 Project metadata in ``.sublime-project`` files
-is split across three top level sections:
+is split across three topmost sections:
 ``folders``, for the included folders; ``settings``,
 for project-specific settings;
 and ``build_systems``, for project-specific build systems.

diff --git a/source/reference/color_schemes.rst b/source/reference/color_schemes.rst
@@ -78,7 +78,7 @@ Structure of a Color Scheme File
 Color scheme files are based
 on the Property List format.
 All color scheme files share
-the same top-level structure.
+the same topmost structure.
 
 Colors can be expressed in the
 following formats: ``#RRGGBB``, ``#RGB``.
@@ -90,7 +90,7 @@ accept an alpha channel value:
 .. contents:: Contents
    :local:
 
-Top-level Elements in Color Schemes Files
+Topmost Elements in Color Schemes Files
 *****************************************
 
 .. code-block:: xml
@@ -136,7 +136,7 @@ These settings affect global visual items
 in the editing area.
 
 Global settings go inside a ``<dict>`` element
-within the top-level ``<array>``.
+within the topmost ``<array>``.
 
 .. code-block:: xml
 

diff --git a/source/reference/comments.rst b/source/reference/comments.rst
@@ -75,7 +75,7 @@ Structure of a Comment Metadata File
 ====================================
 
 All comment metadata files
-share the same top-level structure,
+share the same topmost structure,
 which is inherited from Property List format:
 
 .. code-block:: xml

diff --git a/source/reference/metadata.rst b/source/reference/metadata.rst
@@ -104,7 +104,7 @@ several types of metadata.
 Structure of a Metadata File
 ============================
 
-All metadata files share the same top-level structure,
+All metadata files share the same topmost structure,
 which is inherited from the Property List format.
 
 .. code-block:: xml
@@ -117,7 +117,7 @@ which is inherited from the Property List format.
    </dict>
    </plist>
 
-Sublime Text uses the following top-level keys
+Sublime Text uses the following topmost keys
 in metadata files;
 all others are ignored by default.
 

diff --git a/source/reference/plugins.rst b/source/reference/plugins.rst
@@ -123,7 +123,7 @@ Sublime Text ships with a trimmed down standard library.
 Automatic Plugin Reload
 ***********************
 
-Sublime Text will reload top-level Python modules as they change (perhaps
+Sublime Text will reload topmost Python modules as they change (perhaps
 because you are editing a *.py* file within *Packages*). By contrast, Python
 subpackages won't be reloaded automatically, and this can lead to confusion
 while you're developing plugins. Generally speaking, it's best to restart

diff --git a/source/reference/symbols.rst b/source/reference/symbols.rst
@@ -147,7 +147,7 @@ Structure of a Symbol Definition File
 =====================================
 
 All metadata files
-share the same top-level structure,
+share the same topmost structure,
 which is inherited from the Property List format.
 
 

diff --git a/source/reference/syntaxdefs.rst b/source/reference/syntaxdefs.rst
@@ -67,7 +67,7 @@ import statements in other language definitions.
     interface. It's usually the name of the programming language or equivalent.
 
 ``scopeName``
-    Name of the top-level scope for this syntax definition. Either
+    Name of the topmost scope for this syntax definition. Either
     ``source.<lang>`` or ``text.<lang>``. Use ``source`` for programming
     languages and ``text`` for markup and everything else.