take out currently

website/docs/internals/credentials-helpers.mdx

@@ -140,8 +140,8 @@ stream and then exiting with a non-zero status code.
 
 ## Handling Unsupported Credentials Object Properties
 
-Currently Terraform defines only the `token` property within JSON credentials
-objects, but this format might be extended in future.
+Terraform defines only the `token` property within JSON credentials
+objects.
 
 If a credentials helper is asked to store an object that has any properties
 other than `token` and if it is not able to faithfully retain them then it

website/docs/internals/json-format.mdx

@@ -49,7 +49,7 @@ The JSON output format consists of the following objects and sub-objects:
 
 ## State Representation
 
-Because state does not currently have any significant metadata not covered by the common values representation ([described below](#values-representation)), the `<state-representation>` is straightforward:
+Because state does not  have any significant metadata not covered by the common values representation ([described below](#values-representation)), the `<state-representation>` uses the following format:
 
 ```javascript
 {
@@ -612,7 +612,7 @@ A `<change-representation>` describes the change to the indicated object.
 
 ## Checks Representation
 
-~> **Warning:** The JSON representation of "checks" is currently experimental
+~> **Warning:** The JSON representation of "checks" is experimental
 and some details may change in future Terraform versions based on feedback,
 even in minor releases of Terraform CLI.
 
@@ -627,8 +627,7 @@ A `<checks-representation>` describes the current state of a checkable object in
       // "kind" specifies what kind of checkable object this is. Different
       // kinds of object will have different additional properties inside the
       // address object, but all kinds include both "kind" and "to_display".
-      // Currently the two valid kinds are "resource" and "output_value", but
-      // additional kinds may be added in future Terraform versions.
+      // The two valid kinds are "resource" and "output_value".
       "kind": "resource",
 
       // "to_display" contains an opaque string representation of the address

website/docs/internals/login-protocol.mdx

@@ -51,7 +51,7 @@ The properties within the discovery object are as follows:
   specific mechanism by which an OAuth server authenticates the request and
   issues an authorization token.
 
-  Terraform CLI currently only supports a single grant type:
+  Terraform CLI supports a single grant type:
 
   * `authz_code`: [authorization code grant](https://tools.ietf.org/html/rfc6749#section-4.1).
     Both the `authz` and `token` properties are required when `authz_code` is

website/docs/internals/machine-readable-ui.mdx

@@ -136,7 +136,7 @@ At the end of a plan or before an apply, Terraform will emit a `planned_change`
 - `resource`: object describing the address of the resource to be changed; see [resource object](#resource-object) below for details
 - `previous_resource`: object describing the previous address of the resource, if this change includes a configuration-driven move
 - `action`: the action planned to be taken for the resource. Values: `noop`, `create`, `read`, `update`, `replace`, `delete`, `move`.
-- `reason`: an optional reason for the change, currently only used when the action is `replace` or `delete`. Values:
+- `reason`: an optional reason for the change, only used when the action is `replace` or `delete`. Values:
   - `tainted`: resource was marked as tainted
   - `requested`: user requested that the resource be replaced, for example via the `-replace` plan flag
   - `cannot_update`: changes to configuration force the resource to be deleted and created rather than updated

website/docs/internals/module-registry-protocol.mdx

@@ -147,9 +147,7 @@ $ curl 'https://registry.terraform.io/v1/modules/hashicorp/consul/aws/versions'
 The `modules` array in the response always includes the requested module as the
 first element.
 
-Other elements of this list are not currently used. Third-party implementations
-should always use a single-element list for forward compatiblity with possible
-future extensions to the protocol.
+Terraform does not use the other elements of this list. However, third-party implementations should always use a single-element list for forward compatiblity.
 
 Each returned module has an array of available versions, which Terraform
 matches against any version constraints given in configuration.

website/docs/internals/provider-network-mirror-protocol.mdx

@@ -149,9 +149,7 @@ A successful result is a JSON object containing a single property `versions`,
 which must be a JSON object.
 
 Each of the property names of the `versions` object represents an available
-version number. The property values must be objects, but no properties are
-currently defined for those objects. We recommend leaving those objects
-empty.
+version number. The property values must be objects, but no properties are defined for those objects. We recommend leaving those objects empty.
 
 Return `404 Not Found` to signal that the mirror does not have a provider
 with the given address.

website/docs/internals/provider-registry-protocol.mdx

@@ -294,11 +294,11 @@ A successful result is a JSON object with the following properties:
   _required_ for describing an individual provider package so that Terraform
   CLI can avoid downloading a package that will not be compatible with it.
 
-* `os` (required): this must currently echo back the `os` parameter from the
-  request. Other possibilities may come in later versions of this protocol.
+* `os` (required): this must echo back the `os` parameter from the
+  request.
 
-* `arch` (required): this must currently echo back the `arch` parameter from the
-  request. Other possibilities may come in later versions of this protocol.
+* `arch` (required): this must echo back the `arch` parameter from the
+  request. 
 
 * `filename` (required): the filename for this provider's zip archive as
   recorded in the "shasums" document, so that Terraform CLI can determine which