From 57bd5f374f26cdb7ae1b1c92fd6eb71335b9805b Mon Sep 17 00:00:00 2001 From: Masayuki Morita Date: Tue, 23 Jul 2019 04:50:19 +0900 Subject: [PATCH] Fix typos (#85) --- README.md | 2 +- ext/dynblock/README.md | 2 +- guide/go_expression_eval.rst | 2 +- hcl/hclsyntax/spec.md | 2 +- hcl/spec.md | 4 ++-- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 9ae0baf..d980c88 100644 --- a/README.md +++ b/README.md @@ -56,7 +56,7 @@ such as Ruby. HCL syntax is designed to be easily read and written by humans, and allows _declarative_ logic to permit its use in more complex applications. HCL is intended as a base syntax for configuration formats built -around key-value pairs and heirarchical blocks whose structure is well-defined +around key-value pairs and hierarchical blocks whose structure is well-defined by the calling application, and this definition of the configuration structure allows for better error messages and more convenient definition within the calling application. diff --git a/ext/dynblock/README.md b/ext/dynblock/README.md index 2b24fdb..f59ce92 100644 --- a/ext/dynblock/README.md +++ b/ext/dynblock/README.md @@ -95,7 +95,7 @@ schema model provides a description of only one level of nested blocks at a time, and thus a new schema must be provided for each additional level of nesting. -To make this arduous process as convenient as possbile, this package provides +To make this arduous process as convenient as possible, this package provides a helper function `WalkForEachVariables`, which returns a `WalkVariablesNode` instance that can be used to find variables directly in a given body and also determine which nested blocks require recursive calls. Using this mechanism diff --git a/guide/go_expression_eval.rst b/guide/go_expression_eval.rst index f6ed0b6..df0d1d4 100644 --- a/guide/go_expression_eval.rst +++ b/guide/go_expression_eval.rst @@ -93,7 +93,7 @@ available in a ``stdlib`` package within the :go:pkg:`cty` repository, avoiding the need for each application to re-implement basic functions for string manipulation, list manipulation, etc. It also includes function-shaped versions of several operations that are native operators in HCL, which should generally -*not* be exposed as functions in HCL-based configurationf formats to avoid user +*not* be exposed as functions in HCL-based configuration formats to avoid user confusion. You can define functions in the ``Functions`` field of :go:type:`hcl.EvalContext`: diff --git a/hcl/hclsyntax/spec.md b/hcl/hclsyntax/spec.md index 091c1c2..d7faeed 100644 --- a/hcl/hclsyntax/spec.md +++ b/hcl/hclsyntax/spec.md @@ -187,7 +187,7 @@ for later evaluation by the calling application. ### Blocks A _block_ creates a child body that is annotated with a block _type_ and -zero or more block _labels_. Blocks create a structural hierachy which can be +zero or more block _labels_. Blocks create a structural hierarchy which can be interpreted by the calling application. Block labels can either be quoted literal strings or naked identifiers. diff --git a/hcl/spec.md b/hcl/spec.md index 8bbaff8..97ef613 100644 --- a/hcl/spec.md +++ b/hcl/spec.md @@ -66,7 +66,7 @@ _block header schemata_: Within a schema, it is an error to request the same attribute name twice or to request a block type whose name is also an attribute name. While this can in principle be supported in some syntaxes, in other syntaxes the attribute -and block namespaces are combined and so an an attribute cannot coexist with +and block namespaces are combined and so an attribute cannot coexist with a block whose type name is identical to the attribute name. The result of applying a body schema to a body is _body content_, which @@ -497,7 +497,7 @@ producing an unknown value of the target type. Conversion of any value _to_ the dynamic pseudo-type is a no-op. The result is the input value, verbatim. This is the only situation where the conversion -result value is not of the the given target type. +result value is not of the given target type. ### Primitive Type Conversions