ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #734 from ceh/spell 

website: address spelling mistakes, casing and links
This commit is contained in:
Seth Vargo 2015-01-03 14:09:16 -05:00
parent 8e4f9f472f 28d39cd0bc
commit 15937fb275
35 changed files with 68 additions and 68 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
website/source/community.html.erb
View File

@ -40,9 +40,9 @@ disappear from this list as contributors come and go.
Mitchell Hashimoto is the creator of Terraform and works on all
layers of Terraform from the core to providers. In addition to Terraform,
Mitchell is the creator of
<a href="http://www.vagrantup.com">Vagrant</a>,
<a href="http://www.packer.io">Packer</a>, and
<a href="http://www.consul.io">Consul</a>.
<a href="https://www.vagrantup.com">Vagrant</a>,
<a href="https://www.packer.io">Packer</a>, and
<a href="https://www.consul.io">Consul</a>.
</p>
</div>
</div>
@ -55,8 +55,8 @@ disappear from this list as contributors come and go.
Armon Dadgar is a creator of Terraform. He created valuable sections
of the core and helps maintain providers as well. Armon is also the
creator of
<a href="http://www.consul.io">Consul</a>,
<a href="http://www.serfdom.io">Serf</a>,
<a href="https://www.consul.io">Consul</a>,
<a href="https://www.serfdom.io">Serf</a>,
<a href="https://github.com/armon/statsite">Statsite</a>, and
<a href="https://github.com/armon/bloomd">Bloomd</a>.
</p>
@ -71,10 +71,10 @@ disappear from this list as contributors come and go.
Jack Pearkes is a creator of Terraform. He created and maintains
most of the providers and documentation.
He is also a core committer to
<a href="http://www.packer.io">Packer</a> and
<a href="http://www.consul.io">Consul</a>
<a href="https://www.packer.io">Packer</a> and
<a href="https://www.consul.io">Consul</a>
while also being an employee of
<a href="http://www.hashicorp.com">HashiCorp</a>.
<a href="https://www.hashicorp.com">HashiCorp</a>.
</p>
</div>
</div>

4
website/source/docs/commands/show.html.markdown
View File

@ -3,7 +3,7 @@ layout: "docs"
page_title: "Command: show"
sidebar_current: "docs-commands-show"
description: |-
The `terraform show` command is used to provide human-readable output from a state or plan file. This can be used to inspect a plan to ensure that the planned operations are expected, or to inspect the current state as terraform sees it.
The `terraform show` command is used to provide human-readable output from a state or plan file. This can be used to inspect a plan to ensure that the planned operations are expected, or to inspect the current state as Terraform sees it.
---
# Command: show
@ -11,7 +11,7 @@ description: |-
The `terraform show` command is used to provide human-readable output
from a state or plan file. This can be used to inspect a plan to ensure
that the planned operations are expected, or to inspect the current state
as terraform sees it.
as Terraform sees it.
## Usage

2
website/source/docs/configuration/syntax.html.md
View File

@ -60,7 +60,7 @@ Basic bullet point reference:
* Numbers can be suffixed with `kKmMgG` for some multiple of 10.
For example: `1k` is equal to `1000`.
* Numbers can be suffxed with `[kKmMgG]b` for power of 2 multiples,
* Numbers can be suffixed with `[kKmMgG]b` for power of 2 multiples,
example: `1kb` is equal to `1024`.
* Boolean values: `true`, `false`, `on`, `off`, `yes`, `no`.

4
website/source/docs/modules/index.html.markdown
View File

@ -3,12 +3,12 @@ layout: "docs"
page_title: "Modules"
sidebar_current: "docs-modules"
description: |-
Modules in terraform are self-contained packages of Terraform configurations that are managed as a group. Modules are used to create reusable components in Terraform as well as for basic code organization.
Modules in Terraform are self-contained packages of Terraform configurations that are managed as a group. Modules are used to create reusable components in Terraform as well as for basic code organization.
---
# Modules
Modules in terraform are self-contained packages of Terraform configurations
Modules in Terraform are self-contained packages of Terraform configurations
that are managed as a group. Modules are used to create reusable components
in Terraform as well as for basic code organization.

6
website/source/docs/modules/sources.html.markdown
View File

@ -3,15 +3,15 @@ layout: "docs"
page_title: "Module Sources"
sidebar_current: "docs-modules-sources"
description: |-
As documented in usage, the only required parameter when using a module is the `source` paramter which tells Terraform where the module can be found and what constraints to put on the module if any (such as branches for git, versions, etc.).
As documented in usage, the only required parameter when using a module is the `source` parameter which tells Terraform where the module can be found and what constraints to put on the module if any (such as branches for Git, versions, etc.).
---
# Module Sources
As documented in [usage](/docs/modules/usage.html), the only required
parameter when using a module is the `source` paramter which tells Terraform
parameter when using a module is the `source` parameter which tells Terraform
where the module can be found and what constraints to put on the module
if any (such as branches for git, versions, etc.).
if any (such as branches for Git, versions, etc.).
Terraform manages modules for you: it downloads them, organizes them
on disk, checks for updates, etc. Terraform uses this source parameter for

2
website/source/docs/providers/atlas/r/artifact.html.markdown
View File

@ -73,7 +73,7 @@ The following attributes are exported:
* `id` - The ID of the artifact. This could be an AMI ID, GCE Image ID, etc.
* `file_url` - For artifacts that are binaries, this is a download path.
* `metadata_full` - Contains the full metadata of the artifact. The keys are sanitized
to replace any characters that are invalid in a resource name with a hypen.
to replace any characters that are invalid in a resource name with a hyphen.
For example, the "region.us-east-1" key will become "region-us-east-1".
* `version_real` - The matching version of the artifact
* `slug` - The artifact slug in Atlas

2
website/source/docs/providers/aws/r/network_acl.html.markdown
View File

@ -43,7 +43,7 @@ The following arguments are supported:
* `vpc_id` - (Required) The ID of the associated VPC.
* `subnet_id` - (Optional) The ID of the associated subnet.
* `ingress` - (Optional) Specifies an ingress rule. Parameters defined below.
* `egress` - (Optional) Speicifes an egress rule. Parameters defined below.
* `egress` - (Optional) Specifies an egress rule. Parameters defined below.
Both `egress` and `ingress` support the following keys:

4
website/source/docs/providers/cloudflare/r/record.html.markdown
View File

@ -32,7 +32,7 @@ The following arguments are supported:
* `value` - (Required) The value of the record
* `type` - (Required) The type of the record
* `ttl` - (Optional) The TTL of the record
* `priority` - (Optional) The TTL of the record
* `priority` - (Optional) The priority of the record
## Attributes Reference
@ -42,7 +42,7 @@ The following attributes are exported:
* `name` - The name of the record
* `value` - The value of the record
* `type` - The type of the record
* `ttl` - The ttl of the record
* `ttl` - The TTL of the record
* `priority` - The priority of the record
* `hostname` - The FQDN of the record

4
website/source/docs/providers/cloudstack/index.html.markdown
View File

@ -3,14 +3,14 @@ layout: "cloudstack"
page_title: "Provider: CloudStack"
sidebar_current: "docs-cloudstack-index"
description: |-
The CloudStack provider is used to interact with the many resources supported by CloudStack. The provider needs to be configured with a URL pointing to a runnning CloudStack API and the proper credentials before it can be used.
The CloudStack provider is used to interact with the many resources supported by CloudStack. The provider needs to be configured with a URL pointing to a running CloudStack API and the proper credentials before it can be used.
---
# CloudStack Provider
The CloudStack provider is used to interact with the many resources
supported by CloudStack. The provider needs to be configured with a
URL pointing to a runnning CloudStack API and the proper credentials
URL pointing to a running CloudStack API and the proper credentials
before it can be used.
Use the navigation to the left to read about the available resources.

10
website/source/docs/providers/cloudstack/r/firewall.html.markdown
View File

@ -3,12 +3,12 @@ layout: "cloudstack"
page_title: "CloudStack: cloudstack_firewall"
sidebar_current: "docs-cloudstack-resource-firewall"
description: |-
Creates firewall rules for a given ip address.
Creates firewall rules for a given IP address.
---
# cloudstack\_firewall
Creates firewall rules for a given ip address.
Creates firewall rules for a given IP address.
## Example Usage
@ -28,7 +28,7 @@ resource "cloudstack_firewall" "default" {
The following arguments are supported:
* `ipaddress` - (Required) The ip address for which to create the firewall rules.
* `ipaddress` - (Required) The IP address for which to create the firewall rules.
Changing this forces a new resource to be created.
* `rule` - (Required) Can be specified multiple times. Each rule block supports
@ -36,7 +36,7 @@ The following arguments are supported:
The `rule` block supports:
* `source_cidr` - (Required) The source cidr to allow access to the given ports.
* `source_cidr` - (Required) The source CIDR to allow access to the given ports.
* `protocol` - (Required) The name of the protocol to allow. Valid options are:
`tcp`, `udp` and `icmp`.
@ -54,4 +54,4 @@ The `rule` block supports:
The following attributes are exported:
* `ipaddress` - The ip address for which the firewall rules are created.
* `ipaddress` - The IP address for which the firewall rules are created.

10
website/source/docs/providers/cloudstack/r/ipaddress.html.markdown
View File

@ -23,10 +23,10 @@ resource "cloudstack_ipaddress" "default" {
The following arguments are supported:
* `network` - (Optional) The name of the network for which an IP address should
be aquired and accociated. Changing this forces a new resource to be created.
be acquired and associated. Changing this forces a new resource to be created.
* `vpc` - (Optional) The name of the vpc for which an IP address should
be aquired and accociated. Changing this forces a new resource to be created.
* `vpc` - (Optional) The name of the VPC for which an IP address should
be acquired and associated. Changing this forces a new resource to be created.
*NOTE: Either `network` or `vpc` should have a value!*
@ -34,5 +34,5 @@ The following arguments are supported:
The following attributes are exported:
* `id` - The ID of the aquired and accociated IP address.
* `ipaddress` - The IP address that was aquired and accociated.
* `id` - The ID of the acquired and associated IP address.
* `ipaddress` - The IP address that was acquired and associated.

2
website/source/docs/providers/cloudstack/r/network.html.markdown
View File

@ -37,7 +37,7 @@ The following arguments are supported:
* `network_offering` - (Required) The name of the network offering to use for
this network.
* `vpc` - (Optional) The name of the vpc to create this network for. Changing
* `vpc` - (Optional) The name of the VPC to create this network for. Changing
this forces a new resource to be created.
* `aclid` - (Optional) The ID of a network ACL that should be attached to the

2
website/source/docs/providers/cloudstack/r/network_acl.html.markdown
View File

@ -43,7 +43,7 @@ The following arguments are supported:
* `vpc_id` - (Required) The ID of the associated VPC.
* `subnet_id` - (Optional) The ID of the associated subnet.
* `ingress` - (Optional) Specifies an ingress rule. Parameters defined below.
* `egress` - (Optional) Speicifes an egress rule. Parameters defined below.
* `egress` - (Optional) Specifies an egress rule. Parameters defined below.
Both `egress` and `ingress` support the following keys:

2
website/source/docs/providers/cloudstack/r/network_acl_rule.html.markdown
View File

@ -41,7 +41,7 @@ The `rule` block supports:
* `action` - (Optional) The action for the rule. Valid options are: `allow` and
`deny` (defaults allow).
* `source_cidr` - (Required) The source cidr to allow access to the given ports.
* `source_cidr` - (Required) The source CIDR to allow access to the given ports.
* `protocol` - (Required) The name of the protocol to allow. Valid options are:
`tcp`, `udp`, `icmp`, `all` or a valid protocol number.

4
website/source/docs/providers/cloudstack/r/port_forward.html.markdown
View File

@ -29,7 +29,7 @@ resource "cloudstack_port_forward" "default" {
The following arguments are supported:
* `ipaddress` - (Required) The ip address for which to create the port forwards.
* `ipaddress` - (Required) The IP address for which to create the port forwards.
Changing this forces a new resource to be created.
* `forward` - (Required) Can be specified multiple times. Each forward block supports
@ -50,4 +50,4 @@ The `forward` block supports:
The following attributes are exported:
* `ipaddress` - The ip address for which the port forwards are created.
* `ipaddress` - The IP address for which the port forwards are created.

2
website/source/docs/providers/consul/index.html.markdown
View File

@ -8,7 +8,7 @@ description: |-
# Consul Provider
[Consul](http://www.consul.io) is a tool for service discovery, configuration
[Consul](https://www.consul.io) is a tool for service discovery, configuration
and orchestration. The Consul provider exposes resources used to interact with a
Consul cluster. Configuration of the provider is optional, as it provides
defaults for all arguments.

2
website/source/docs/providers/dnsimple/r/record.html.markdown
View File

@ -41,7 +41,7 @@ The following attributes are exported:
* `name` - The name of the record
* `value` - The value of the record
* `type` - The type of the record
* `ttl` - The ttl of the record
* `ttl` - The TTL of the record
* `priority` - The priority of the record
* `domain_id` - The domain ID of the record
* `hostname` - The FQDN of the record

2
website/source/docs/providers/google/r/compute_route.html.markdown
View File

@ -63,7 +63,7 @@ The following arguments are supported:
The following attributes are exported:
* `name` - The name of the resource.
* `dest_range` - The detination CIDR block of this route.
* `dest_range` - The destination CIDR block of this route.
* `network` - The name of the network of this route.
* `next_hop_ip` - The IP address of the next hop, if available.
* `next_hop_instance` - The name of the instance of the next hop, if available.

2
website/source/docs/providers/heroku/r/addon.html.markdown
View File

@ -14,7 +14,7 @@ services to a Heroku app.
## Example Usage
```
# Create a new heroku app
# Create a new Heroku app
resource "heroku_app" "default" {
name = "test-app"
}

2
website/source/docs/providers/heroku/r/app.html.markdown
View File

@ -14,7 +14,7 @@ create and manage applications on Heroku.
## Example Usage
```
# Create a new heroku app
# Create a new Heroku app
resource "heroku_app" "default" {
name = "my-cool-app"

4
website/source/docs/providers/heroku/r/cert.html.markdown
View File

@ -13,7 +13,7 @@ Provides a Heroku SSL certificate resource. It allows to set a given certificate
## Example Usage
```
# Create a new heroku app
# Create a new Heroku app
resource "heroku_app" "default" {
name = "test-app"
}
@ -46,6 +46,6 @@ The following arguments are supported:
The following attributes are exported:
* `id` - The ID of the add-on
* `cname` - The CNAME of ssl endpoint
* `cname` - The CNAME for the SSL endpoint
* `name` - The name of the SSL certificate

8
website/source/docs/providers/heroku/r/domain.html.markdown
View File

@ -14,7 +14,7 @@ create and manage applications on Heroku.
## Example Usage
```
# Create a new heroku app
# Create a new Heroku app
resource "heroku_app" "default" {
name = "test-app"
}
@ -37,7 +37,7 @@ The following arguments are supported:
The following attributes are exported:
* `id` - The ID of the of the domain record
* `hostname` - The hostname traffic will be served as
* `cname` - The cname traffic should route to.
* `id` - The ID of the of the domain record.
* `hostname` - The hostname traffic will be served as.
* `cname` - The CNAME traffic should route to.

4
website/source/docs/providers/heroku/r/drain.html.markdown
View File

@ -24,12 +24,12 @@ resource "heroku_drain" "default" {
The following arguments are supported:
* `url` - (Required) The URL for Heroku to drain your logs to
* `url` - (Required) The URL for Heroku to drain your logs to.
* `app` - (Required) The Heroku app to link to.
## Attributes Reference
The following attributes are exported:
* `token` - The unique token for your created drain
* `token` - The unique token for your created drain.

8
website/source/docs/providers/mailgun/r/domain.html.markdown
View File

@ -14,7 +14,7 @@ create and manage applications on Mailgun.
## Example Usage
```
# Create a new mailgun domain
# Create a new Mailgun domain
resource "mailgun_domain" "default" {
name = "test.example.com"
spam_action = "disabled"
@ -30,8 +30,8 @@ The following arguments are supported:
* `smtp_password` - (Required) Password for SMTP authentication
* `spam_action` - (Optional) `disabled` or `tag` Disable, no spam
filtering will occur for inbound messages. Tag, messages
will be tagged wtih a spam header.
* `wildcard` - (Optional) Boolean determines whether
will be tagged with a spam header.
* `wildcard` - (Optional) Boolean that determines whether
the domain will accept email for sub-domains.
## Attributes Reference
@ -48,7 +48,7 @@ The following attributes are exported:
* `record_type` - The record type.
* `valid` - `"valid"` if the record is valid.
* `value` - The value of the record.
* `sending_records` - An arry of DNS records for sending validation.
* `sending_records` - An array of DNS records for sending validation.
* `name` - The name of the record.
* `record_type` - The record type.
* `valid` - `"valid"` if the record is valid.

2
website/source/intro/examples/aws.html.markdown
View File

@ -18,7 +18,7 @@ To simplify the example, this intentionally ignores deploying and
getting your application onto the servers. However, you could do so either via
[provisioners](/docs/provisioners/index.html) and a configuration
management tool, or by pre-baking configured AMIs with
[Packer](http://www.packer.io).
[Packer](https://www.packer.io).
After you run `terraform apply` on this configuration, it will
automatically output the DNS address of the ELB. After your instance

2
website/source/intro/examples/consul.html.markdown
View File

@ -10,7 +10,7 @@ description: |-
[**Example Contents**](https://github.com/hashicorp/terraform/tree/master/examples/consul)
[Consul](http://www.consul.io) is a tool for service discovery, configuration
[Consul](https://www.consul.io) is a tool for service discovery, configuration
and orchestration. The Key/Value store it provides is often used to store
application configuration and information about the infrastructure necessary
to process requests.

2
website/source/intro/examples/index.html.markdown
View File

@ -13,7 +13,7 @@ of the ways Terraform can be used.
All examples are ready to run as-is. Terraform will
ask for input of things such as variables and API keys. If you want to
conitnue using the example, you should save those parameters in a
continue using the example, you should save those parameters in a
"terraform.tfvars" file or in a `provider` config bock.
~> **Warning!** The examples use real providers that launch _real_ resources.

2
website/source/intro/getting-started/build.html.md
View File

@ -195,7 +195,7 @@ the getting started guide.
The EC2 instance we launched at this point is based on the AMI
given, but has no additional software installed. If you're running
an image-based infrastructure (perhaps creating images with
[Packer](http://www.packer.io)), then this is all you need.
[Packer](https://www.packer.io)), then this is all you need.
However, many infrastructures still require some sort of initialization
or software provisioning step. Terraform supports

2
website/source/intro/getting-started/modules.html.md
View File

@ -33,7 +33,7 @@ configuration files.
As an example, we're going to use the
[Consul Terraform module](#)
which will setup a complete [Consul](http://www.consul.io) cluster
which will setup a complete [Consul](https://www.consul.io) cluster
for us.
Create a configuration file with the following contents:

4
website/source/intro/getting-started/provision.html.md
View File

@ -13,7 +13,7 @@ introduces how to use provisioners to run basic shell scripts on
instances when they're created.
If you're using an image-based infrastructure (perhaps with images
created with [Packer](http://www.packer.io)), then what you've
created with [Packer](https://www.packer.io)), then what you've
learned so far is good enough. But if you need to do some initial
setup on your instances, provisioners let you upload files,
run shell scripts, etc.
@ -35,7 +35,7 @@ resource "aws_instance" "example" {
```
This adds a `provision` block within the `resource` block. Multiple
`provision` blocks can be added to define multiple provisoining steps.
`provision` blocks can be added to define multiple provisioning steps.
Terraform supports
[multiple provisioners](/docs/provisioners/index.html),
but for this example we use the "local-exec" provisioner.

4
website/source/intro/getting-started/variables.html.md
View File

@ -3,14 +3,14 @@ layout: "intro"
page_title: "Input Variables"
sidebar_current: "gettingstarted-variables"
description: |-
You now have enough Terraform knowledge to create useful configurations, but we're still hardcoding access keys, AMIs, etc. To become truly shareable and commitable to version control, we need to parameterize the configurations. This page introduces input variables as a way to do this.
You now have enough Terraform knowledge to create useful configurations, but we're still hardcoding access keys, AMIs, etc. To become truly shareable and committable to version control, we need to parameterize the configurations. This page introduces input variables as a way to do this.
---
# Input Variables
You now have enough Terraform knowledge to create useful
configurations, but we're still hardcoding access keys,
AMIs, etc. To become truly shareable and commitable to version
AMIs, etc. To become truly shareable and committable to version
control, we need to parameterize the configurations. This page
introduces input variables as a way to do this.

2
website/source/intro/use-cases.html.markdown
View File

@ -56,7 +56,7 @@ a tool to manage their services.
#### Software Demos
Modern software is increasingly networked and distributed. Although tools like
[Vagrant](http://www.vagrantup.com/) exist to build virtualized environments
[Vagrant](https://www.vagrantup.com/) exist to build virtualized environments
for demos, it is still very challenging to demo software on real infrastructure
which more closely matches production environments.

4
website/source/layouts/_footer.erb
View File

@ -11,8 +11,8 @@
</div>
<div class="footer-hashi col-sm-5 col-xs-12">
<div class="pull-right">
<span>Copyright &copy; <%= Time.now.year %>. A <a href="http://www.hashicorp.com">HashiCorp</a> Project.</span>
<a class="hashi-logo" href="http://www.hashicorp.com"><i class="hashi-logo"></i></a>
<span>Copyright &copy; <%= Time.now.year %>. A <a href="https://www.hashicorp.com">HashiCorp</a> Project.</span>
<a class="hashi-logo" href="https://www.hashicorp.com"><i class="hashi-logo"></i></a>
</div>
</div>
</div>

2
website/source/layouts/_header.erb
View File

@ -16,7 +16,7 @@
<nav class="collapse navbar-collapse bs-navbar-collapse" role="navigation">
<ul class="buttons nav navbar-nav navbar-right rls-sb">
<li class="first download terra-btn"><a href="/downloads.html">Download</a></li>
<li class="github terra-btn"><a href="https://github.com/hashicorp/terraform">Github</a></li>
<li class="github terra-btn"><a href="https://github.com/hashicorp/terraform">GitHub</a></li>
</ul>
<ul class="main-links nav navbar-nav navbar-right rls-sb">

2
website/source/layouts/google.erb
View File

@ -7,7 +7,7 @@
</li>
<li<%= sidebar_current("docs-google-index") %>>
<a href="/docs/providers/google/index.html">google Provider</a>
<a href="/docs/providers/google/index.html">Google Provider</a>
</li>
<li<%= sidebar_current("docs-google-resource") %>>