Skip to content

Commit 69d9cdb

Browse files
committed
Merge pull request #74 from davebiffuk/patch-1
fix typos in networking.rst
2 parents 027e414 + 85e0367 commit 69d9cdb

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

docs/source/networking.rst

+8-8
Original file line numberDiff line numberDiff line change
@@ -3,22 +3,22 @@
33
Network Configurations
44
======================
55

6-
CfnCluster leverages Amazon Virtual Private Cloud(VPC) for networking. This provides a very flexiable and configurable networking platform to deploy clusters within. CfnCluster support the following high-level configurations:
6+
CfnCluster leverages Amazon Virtual Private Cloud (VPC) for networking. This provides a very flexible and configurable networking platform to deploy clusters within. CfnCluster support the following high-level configurations:
77

88
* Single subnet, master and compute in the same subnet
99
* Two subnets, master in one subnet and compute new private subnet
10-
* Two subnets, master in one subnet and compute in exisiting private subnet
10+
* Two subnets, master in one subnet and compute in existing private subnet
1111

12-
All of these configurations can operate with or without public IP addressing. It can also be deployed to leverage an HTTP proxy for all AWS requests. The combinations of these configurations result in many different deployment scenario's, ranging from a single public subnet with all access over the Internet, to fully private via AWS Direct Connect and HTTP proxy for all traffic.
12+
All of these configurations can operate with or without public IP addressing. It can also be deployed to leverage an HTTP proxy for all AWS requests. The combinations of these configurations result in many different deployment scenarios, ranging from a single public subnet with all access over the Internet, to fully private via AWS Direct Connect and HTTP proxy for all traffic.
1313

14-
Below are some architeture diagrams for some of those scenarios:
14+
Below are some architecture diagrams for some of those scenarios:
1515

1616
.. figure:: images/networking_single_subnet.jpg
1717
:alt: CfnCluster single subnet
1818

1919
CfnCluster in a single public subnet
2020

21-
The configuration for this architecture, requires the following settings:
21+
The configuration for this architecture requires the following settings:
2222

2323
`note that all values are examples only`
2424

@@ -31,9 +31,9 @@ The configuration for this architecture, requires the following settings:
3131
.. figure:: images/networking_two_subnets.jpg
3232
:alt: CfnCluster two subnets
3333

34-
CfnCluster using two subnets(new private)
34+
CfnCluster using two subnets (new private)
3535

36-
The configuration for this architecture, requires the following settings:
36+
The configuration for this architecture requires the following settings:
3737

3838
`note that all values are examples only`
3939

@@ -49,7 +49,7 @@ The configuration for this architecture, requires the following settings:
4949

5050
CfnCluster in a private subnet connected using Direct Connect
5151

52-
The configuration for this architecture, requires the following settings:
52+
The configuration for this architecture requires the following settings:
5353

5454
`note that all values are examples only`
5555

0 commit comments

Comments
 (0)