[brooklyn-docs] branch master updated: Softlayer has been renamed

[du...@apache.org]

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

duncangrant 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 02ad966  Softlayer has been renamed
     new 921d11f  Merge pull request #334 from duncangrant/update-softlayer-ibm-cloud
02ad966 is described below

commit 02ad96620257bbb9b4913aa6e0544dec03ebe6df
Author: Duncan Grant <du...@cloudsoft.io>
AuthorDate: Fri Sep 3 10:15:13 2021 +0100

    Softlayer has been renamed
---
 guide/locations/_ibm-softlayer.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/guide/locations/_ibm-softlayer.md b/guide/locations/_ibm-softlayer.md
index 5cbccae..1413df7 100644
--- a/guide/locations/_ibm-softlayer.md
+++ b/guide/locations/_ibm-softlayer.md
@@ -5,7 +5,7 @@ section_type: inline
 section_position: 6
 ---
 
-## IBM SoftLayer
+## IBM Cloud (previously IBM SoftLayer)
 
 ### Credentials
 
@@ -28,20 +28,20 @@ credential management, for example using [Vault](https://www.vaultproject.io/).
 
 Below are examples of configuration options that use values specific to Softlayer:
 
-* The `region` is the [Softlayer datacenter](http://www.softlayer.com/data-centers).
+* The `region` is the datacenter where the vm will be deployed.
   For example, `region: dal05`.
 
 * The `hardwareId` is an auto-generated combination of the hardware configuration options.
   This is because there is no concept of hardwareId or hardware profile names in Softlayer. 
   An example value is `hardwareId: "cpu=1,memory=1024,disk=25,type=LOCAL"`.
 
-* The `imageId` is the [Image template](https://knowledgelayer.softlayer.com/learning/introduction-image-templates).
+* The `imageId` is the [Image template](https://cloud.ibm.com/docs/image-templates?topic=image-templates-ordering-an-instance-from-an-image-template).
   For example, `imageId: CENTOS_6_64`.
 
 
 ### VLAN Selection
 
-SoftLayer may provision VMs in different VLANs, even within the same region.
+IBM Cloud may provision VMs in different VLANs, even within the same region.
 Some applications require VMs to be on the *same* internal subnet; blueprints
 for these can specify this behaviour in SoftLayer in one of two ways.
 
@@ -119,7 +119,7 @@ are:
 An entity being deployed to a customized location will have the VLAN ids set as
 sensors, with the same names as the last two configuration keys.
 
-***NOTE*** If the SoftLayer location is already configured with specific VLANs
+***NOTE*** If the IBM Cloud location is already configured with specific VLANs
 then this customizer will have no effect.