[GitHub] [brooklyn-docs] algairim commented on a change in pull request #330: Fix broken absolute and relative references; apply consistent referen…

[GitBox <gi...@apache.org>]

algairim commented on a change in pull request #330:
URL: https://github.com/apache/brooklyn-docs/pull/330#discussion_r699552555



##########
File path: guide/blueprints/blueprinting-tips.md
##########
@@ -63,11 +63,6 @@ This is fast and simple, but has some obvious downsides:
 Docker containers provide a convenient way to test blueprints (and also to run blueprints in
 production!).
 
-The [Clocker project](http://www.clocker.io) allows the simple setup of Docker Engine(s), and for Docker
-containers to be used instead of VMs. For testing, this allows each run to start from a fresh 
-container (i.e. no install artifacts from previous runs), while taking advantage of the speed
-of starting containers.
-

Review comment:
       Clocker project does not exist anymore.

##########
File path: guide/ops/gui/blueprints.md
##########
@@ -44,8 +44,6 @@ location:
     credential: s3cr3tsq1rr3ls3cr3tsq1rr3ls3cr3tsq1rr3l
 {% endhighlight %}
 
-**NOTE**: See __[Locations](../locations)__ in the Operations section of the User Guide for instructions on setting up alternate cloud providers, bring-your-own-nodes, or localhost targets, and storing credentials/locations in a file on disk rather than in the blueprint.
-

Review comment:
       This section does not exist anymore.

##########
File path: guide/ops/gui/blueprints.md
##########
@@ -63,10 +61,8 @@ Instead of pasting the YAML blueprint each time, it can be added to the Brooklyn
      rather than extensively document default.catalog.bom.
      also need to include instructions on stopping (currently in help, including stopping apps) -->
 
-See __[Catalog](../catalog/)__ in the Operations section of the User Guide for instructions on creating a new Catalog entry from your Blueprint YAML.

Review comment:
       This section does not exist anymore.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@brooklyn.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org