aboutsummaryrefslogtreecommitdiffstats
path: root/docs/distribution
diff options
context:
space:
mode:
authorramverma <ram.krishna.verma@est.tech>2019-07-11 12:57:49 +0000
committerramverma <ram.krishna.verma@est.tech>2019-07-11 12:57:49 +0000
commit760cce91689a00a52de363c96745323fb95a91b0 (patch)
treecbf618acf5ce8fafcdf8aa1389f06c796941db6c /docs/distribution
parent3b71c9772e0f86b5cef9840668a36569540a037c (diff)
Fix review comments from previous review
Change-Id: Ide96508d2cc616a688d6c1ed524b8317c53aa222 Issue-ID: POLICY-1898 Signed-off-by: ramverma <ram.krishna.verma@est.tech>
Diffstat (limited to 'docs/distribution')
-rw-r--r--docs/distribution/Distribution-User-Manual.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/distribution/Distribution-User-Manual.rst b/docs/distribution/Distribution-User-Manual.rst
index 12f75b9a..7d3f770e 100644
--- a/docs/distribution/Distribution-User-Manual.rst
+++ b/docs/distribution/Distribution-User-Manual.rst
@@ -105,7 +105,7 @@ Build Distribution
.. important::
A Build needs Space
- Building distribution requires approximately 1-2 GB of hard disc space, 100 MB for the actual build with full
+ Building distribution requires approximately 1-2 GB of hard disc space, 100 MB for the actual build with full
distribution and around 1 GB for the downloaded dependencies.
.. important::
@@ -175,7 +175,7 @@ Build Distribution
The build will have created all artifacts required for distribution
installation. The following example show how to change to the target
- directory and how it should look like.
+ directory and how it should look.
+----------------------------------------------------------------------------------------------------------------------------+
| Unix, Cygwin |
@@ -256,7 +256,7 @@ Install Manually from Archive (Windows, 7Zip, GUI)
.. container:: paragraph
- The right-click on the new created TAR file and extract the actual
+ Then right-click on the new created TAR file and extract the actual
distribution.
|
@@ -362,11 +362,11 @@ Introduction to Distribution Configuration
A distribution engine can be configured to use various combinations
of policy reception handlers, policy decoders and policy forwarders.
- The system is build using a plugin architecture. Each configuration
+ The system is built using a plugin architecture. Each configuration
option is realized by a plugin, which can be loaded and
configured when the engine is started. New plugins can be
added to the system at any time, though to benefit from a
- new plugin an engine will need to be restarted.
+ new plugin, an engine will need to be restarted.
|