[brooklyn-docs] branch master updated: removed unneeded over exaplanation

[iu...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

iuliana pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git


The following commit(s) were added to refs/heads/master by this push:
     new 987bf8e  removed unneeded over exaplanation
     new db6087d  Merge pull request #341 from jcabrerizo/feature/fix
987bf8e is described below

commit 987bf8eb55b10738f87b9d301dec94ccf6b4ab3e
Author: Juan Cabrerizo <ju...@cloudsoft.io>
AuthorDate: Fri Sep 10 13:32:31 2021 +0100

    removed unneeded over exaplanation
---
 guide/blueprints/catalog/versioning.md | 2 +-
 guide/start/concept-quickstart.md      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/guide/blueprints/catalog/versioning.md b/guide/blueprints/catalog/versioning.md
index b643ceb..f4c08d6 100644
--- a/guide/blueprints/catalog/versioning.md
+++ b/guide/blueprints/catalog/versioning.md
@@ -122,7 +122,7 @@ hence the bundle replacement noted above.
 
 If you are creating an OSGi `MANIFEST.MF` for a bundle that also contains a `catalog.bom`, 
 you will need to use the mapped result (OSGi version syntax) in the manifest,
-but should continue to use the Brooklyn-recommended syntax in the `catalog.bom`.
+but should continue to use the recommended syntax in the `catalog.bom`.
  
 For those who are curious, the reason for the Brooklyn version syntax is to reconcile
 the popular usage of semver and maven with the internal requirement to use OSGi versions.
diff --git a/guide/start/concept-quickstart.md b/guide/start/concept-quickstart.md
index 970d3c8..e02781c 100644
--- a/guide/start/concept-quickstart.md
+++ b/guide/start/concept-quickstart.md
@@ -14,7 +14,7 @@ The following section provides a quick summary of the main Brooklyn concepts you
 
 ***Applications*** are the top level entities that are the parents of all other entities.
 
-***Configuration*** Entities can have arbitrary configuration values, which get inherited by their child entities. You can set global (Brooklyn-wide) properties in (``~/.brooklyn/brooklyn.properties``).  Common configuration keys have convenient aliases called "flags".
+***Configuration*** Entities can have arbitrary configuration values, which get inherited by their child entities. You can set global properties in (``~/.brooklyn/brooklyn.properties``).  Common configuration keys have convenient aliases called "flags".
 
 ***Sensors*** are the mechanism for entities to expose information for other entities to see.  Sensors from an entity can be subscribed to by other entities to track changes in the entity’s activity. Sensors can be updated, potentially frequently, by the entity or associated tasks.