Fixing incorrect use of "it's" in docs.
This commit is contained in:
parent
e378eaca87
commit
3e844301c5
|
@ -7,7 +7,7 @@ sidebar_current: "docs-commands-refresh"
|
|||
# Command: refresh
|
||||
|
||||
The `terraform refresh` command is used to reconcile the state Terraform
|
||||
knows about (via it's state file) with the real-world infrastructure.
|
||||
knows about (via its state file) with the real-world infrastructure.
|
||||
The can be used to detect any drift from the last-known state, and to
|
||||
update the state file.
|
||||
|
||||
|
|
|
@ -41,7 +41,7 @@
|
|||
<h2 class="feature-t">Combine Multiple Providers</h2>
|
||||
<p>Terraform allows you to effortlessly combine high-level system
|
||||
providers with your own or with each other. Launch a server from
|
||||
one cloud provider, add a DNS entry with it's IP with a different
|
||||
one cloud provider, add a DNS entry with its IP with a different
|
||||
provider. Built-in dependency resolution means
|
||||
things happen in the right order.</p>
|
||||
</div>
|
||||
|
|
|
@ -43,7 +43,7 @@ Terraform both to enable dynamic inputs, but to also store outputs.
|
|||
|
||||
Inputs like AMI name, security groups, puppet roles, bootstrap scripts,
|
||||
etc can all be loaded from Consul. This allows the specifics of an
|
||||
infrastructure to be decoupled from it's overall architecture. This enables
|
||||
infrastructure to be decoupled from its overall architecture. This enables
|
||||
details to be changed without updating the Terraform configuration.
|
||||
|
||||
Outputs from Terraform can also be easily stored in Consul. One powerful
|
||||
|
|
|
@ -8,7 +8,7 @@ sidebar_current: "use-cases"
|
|||
|
||||
Before understanding use cases, it's useful to know [what Terraform is](/intro/index.html).
|
||||
This page lists some concrete use cases for Terraform, but the possible use cases are
|
||||
much broader than what we cover. Due to it's extensible nature, providers and provisioners
|
||||
much broader than what we cover. Due to its extensible nature, providers and provisioners
|
||||
can be added to further extend Terraform's ability to manipulate resources.
|
||||
|
||||
#### Heroku App Setup
|
||||
|
|
|
@ -17,7 +17,7 @@ multiple providers and services to be combined and composed. For example,
|
|||
Terraform can be used to orchestrate an AWS and OpenStack cluster simultaneously,
|
||||
while enabling 3rd party services like CloudFlare and DNSimple to be integrated
|
||||
to provide CDN and DNS services. This enables Terraform to represent and
|
||||
manage the entire infrastructure with it's supporting services, instead of
|
||||
manage the entire infrastructure with its supporting services, instead of
|
||||
only the subset that exists within a single provider. It provides a single
|
||||
unified syntax, instead of requiring operators to use independent and
|
||||
non-interoperable tools for each platform and service.
|
||||
|
|
|
@ -30,7 +30,7 @@ of building the tool allows operators to focus on their infrastructure
|
|||
and not the tooling.
|
||||
|
||||
Additionally, Terraform is an open source tool. In addition to
|
||||
HashiCorp, the community around it helps to extend it's features,
|
||||
HashiCorp, the community around it helps to extend its features,
|
||||
fix bugs and document new use cases. Terraform helps solve a problem
|
||||
that exists in every organization and provides a standard that can
|
||||
be adopted to avoid re-inventing the wheel between and within organizations.
|
||||
|
|
|
@ -11,7 +11,7 @@ allows for representing everything from physical hardware, virtual machines,
|
|||
containers, to email and DNS providers. Because of this flexibility, Terraform
|
||||
can be used to solve many different problems. This means there are a number of
|
||||
existing tools that overlap with the capabilities of Terraform. We compare Terraform
|
||||
to a number of these tools, but it's should be noted that Terraform is not mutual
|
||||
to a number of these tools, but it should be noted that Terraform is not mutual
|
||||
exclusive with other systems. It can be used to manage a single application, or the
|
||||
entire datacenter.
|
||||
|
||||
|
|
Loading…
Reference in New Issue