[3/4] brooklyn-docs git commit: PR #256: incorporate review comments

[tb...@apache.org]

PR #256: incorporate review comments


Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/42190285
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/42190285
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/42190285

Branch: refs/heads/master
Commit: 4219028575474d5fc43b6f28e4b1ed5d0e3adfe9
Parents: 093f483
Author: Aled Sage <al...@gmail.com>
Authored: Mon Jun 4 21:57:03 2018 +0100
Committer: Aled Sage <al...@gmail.com>
Committed: Mon Jun 4 21:57:03 2018 +0100

----------------------------------------------------------------------
 guide/ops/troubleshooting/connectivity.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/42190285/guide/ops/troubleshooting/connectivity.md
----------------------------------------------------------------------
diff --git a/guide/ops/troubleshooting/connectivity.md b/guide/ops/troubleshooting/connectivity.md
index 7b0daf4..82917c2 100644
--- a/guide/ops/troubleshooting/connectivity.md
+++ b/guide/ops/troubleshooting/connectivity.md
@@ -105,7 +105,7 @@ example, execute `sudo iptables -n --list` and `iptables -t nat -n --list`.
 Some clouds offer a firewall service, where ports need to be explicitly listed to be reachable.
 
 For example, 
-[security groups for EC2-classic](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) 
+[security groups for AWS EC2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) 
 have rules for the protocols and ports to be reachable from specific CIDRs.
 
 Check these settings via the cloud provider's web-console (or API).