From 362d8c323a6abe108bf653181270571c187f1d84 Mon Sep 17 00:00:00 2001 From: Anil Kumar Myla Date: Mon, 30 Apr 2018 23:53:41 -0700 Subject: [PATCH] More grammar changes in docs --- src/sphinx/archetypes/index.rst | 4 ++-- src/sphinx/index.rst | 2 +- src/sphinx/introduction.rst | 8 ++++---- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/src/sphinx/archetypes/index.rst b/src/sphinx/archetypes/index.rst index 9a016f122..5167e6298 100644 --- a/src/sphinx/archetypes/index.rst +++ b/src/sphinx/archetypes/index.rst @@ -7,8 +7,8 @@ Archetype plugins provide predefined configurations for your build. Like :ref:`f archetype plugins can depend on other archetype plugins to extend existing functionality. Project archetypes are default deployment scripts that try to "do the right thing" for a given type of project. -Because not all projects are created equal, there is no one single archetype for all native packages, but a set -of them for usage. +Because not all projects are created equal, there is no single archetype for all native packages, but a set +of them to choose from. .. toctree:: :maxdepth: 1 diff --git a/src/sphinx/index.rst b/src/sphinx/index.rst index 624d40089..fc6452f00 100644 --- a/src/sphinx/index.rst +++ b/src/sphinx/index.rst @@ -11,7 +11,7 @@ needed to generate the best package possible. Read the :ref:`introduction` to learn how native-packager works. The :ref:`getting-started` guide will help you set up your first package. The :ref:`packaging-formats` and :ref:`archetypes` sections explain the different plugins in more -detail, which :ref:`recipes` provides solutions for common configurations. +detail, while :ref:`recipes` provide solutions for common configurations. Sitemap diff --git a/src/sphinx/introduction.rst b/src/sphinx/introduction.rst index e9b1486e9..b2b6c179e 100644 --- a/src/sphinx/introduction.rst +++ b/src/sphinx/introduction.rst @@ -53,7 +53,7 @@ These things are **out of native packagers scope** packager. 2. Providing deployment configurations - Native packager produces artefacts with the ``packageBin`` task. What you do with these is part of another step in + Native packager produces artifacts with the ``packageBin`` task. What you do with these is part of another step in your process. @@ -65,7 +65,7 @@ Core Concepts Native packager is based on a few simple concepts. If you understand these, you will be able to customize your build, create own packaging formats and deploy more effectively. -1. **Separation of concerns** of the two plugin kinds +1. **Separation of concerns** with two kinds of plugins - :ref:`format plugins ` define **how** a package is created - :ref:`archetype plugins ` define **what** a package should contain @@ -93,7 +93,7 @@ Format plugins provide the implementation to create package, the **how** a packa start with the plugin name, e.g. *rpmXYZ*. 3. Implement package task - The ``packageBin`` or ``publishLocal`` ( docker ) task provides the actual action to create a package. + ``packageBin`` or ``publishLocal`` tasks provide the actual action to create a package. By enabling a format plugin only with @@ -116,7 +116,7 @@ A full list of archetypes can be found An archetype may provide the following: - 1. New, archetype related settings and tasks + 1. Archetype related settings and tasks 2. New files in your package By enabling an archetype plugin with