Updating cloud-run-v2 terraform and some typos (#2201)

* Updating cloud-run-v2 terraform and some typos

Updating modules/cloud-run-v2/main.tf to determine the tcp_socket value

Fixin typos in:
tests/fixtures.py
modules/workstation-cluster/README.md
modules/net-lb-int/README.md
modules/dataplex/README.md
modules/dataform-repository/README.md
modules/__docs/20230816-iam-refactor.md
CONTRIBUTING.md
blueprints/third-party-solutions/f5-bigip/f5-bigip-ha-active/startup-script.tpl
blueprints/third-party-solutions/f5-bigip/f5-bigip-ha-active/README.md

* Update README.md

---------

Co-authored-by: Ludovico Magnocavallo <ludomagno@google.com>
Co-authored-by: Ludovico Magnocavallo <ludo@qix.it>

CONTRIBUTING.md

@@ -1209,7 +1209,7 @@ The script will create in `<directory>` following structure:
 
 The `infra` directory contains the sandbox infrastructure as well as all environment variables dumped into `terraform.tfvars` file. The script runs `terraform init` and `terraform apply -auto-approve` in this folder.
 
-The `<direcotry>` has empty `main.tf` where you can paste any example, and it will get all necessary variables from `e2e_tests.auto.tfvars` file.
+The `<directory>` has empty `main.tf` where you can paste any example, and it will get all necessary variables from `e2e_tests.auto.tfvars` file.
 
 If there are any changes to the test sandbox, you can rerun the script and only changes will be applied to the project.
 

blueprints/third-party-solutions/f5-bigip/f5-bigip-ha-active/README.md

@@ -344,7 +344,7 @@ module "f5-lb" {
 
 ## F5 code copyright
 
-This repository usees code from the third-party project [terraform-gcp-bigip-module](https://github.com/F5Networks/terraform-gcp-bigip-module).
+This repository uses code from the third-party project [terraform-gcp-bigip-module](https://github.com/F5Networks/terraform-gcp-bigip-module).
 
 This code is also licensed as Apache 2.0.
 

blueprints/third-party-solutions/f5-bigip/f5-bigip-ha-active/startup-script.tpl

@@ -1,6 +1,6 @@
 # Copyright 2014-2019 F5 Networks Inc.
 #
-# This file usees code from the following third-party project:
+# This file uses code from the following third-party project:
 # * [terraform-gcp-bigip-module] - [https://github.com/F5Networks/terraform-gcp-bigip-module]
 #
 # The code from this project is licensed under the Apache 2.0 license.

modules/__docs/20230816-iam-refactor.md

@@ -60,7 +60,7 @@ This variable will not be internally merged in modules with `iam` or `group_iam`
 
 ### Additive bindings
 
-Additive bindings have evolved to mimick authoritative ones, but the result is an interface which is bloated (no one uses `iam_additive_members`), and hard to understand and use without triggering dynamic errors. Coverage is also spotty and uneven across modules, and the interface needs to support aliasing of project service accounts in the project module to work around dynamic errors.
+Additive bindings have evolved to mimic authoritative ones, but the result is an interface which is bloated (no one uses `iam_additive_members`), and hard to understand and use without triggering dynamic errors. Coverage is also spotty and uneven across modules, and the interface needs to support aliasing of project service accounts in the project module to work around dynamic errors.
 
 The `iam_additive` variable is used in a special patterns in data blueprints, to allow code to not mess up existing IAM bindings in an external project on destroy. This pattern only works in a limited set of cases, where principals are passed in via static variables or refer to "magic" static outputs in our modules. This is a simple example of the pattern:
 

modules/dataform-repository/README.md

@@ -7,7 +7,7 @@ This module allows managing a dataform repository, allows adding IAM permissions
 
 ## Examples
 
-### Simple dataform repository with access configration
+### Simple dataform repository with access configuration
 
 Simple dataform repository and specifying repository access via the IAM variable.
 

modules/dataplex/README.md

@@ -1,4 +1,4 @@
-# Dataplex instance with lake, zone & assests
+# Dataplex instance with lake, zone & assets
 
 This module manages the creation of Dataplex instance along with lake, zone & assets in single regions.
 

modules/net-lb-int/README.md

@@ -7,7 +7,7 @@ This module allows managing a GCE Internal Load Balancer and integrates the forw
   - [Referencing existing MIGs](#referencing-existing-migs)
   - [Externally managed instances](#externally-managed-instances)
   - [Passing multiple protocols through the load balancers](#passing-multiple-protocols-through-the-load-balancers)
-  - [Mutiple forwarding rules](#mutiple-forwarding-rules)
+  - [Multiple forwarding rules](#multiple-forwarding-rules)
   - [Dual stack (IPv4 and IPv6)](#dual-stack-ipv4-and-ipv6)
   - [PSC service attachments](#psc-service-attachments)
   - [End to end example](#end-to-end-example)
@@ -146,7 +146,7 @@ module "ilb" {
 # tftest modules=1 resources=4
 ```
 
-### Mutiple forwarding rules
+### Multiple forwarding rules
 
 You can add more forwarding rules to your load balancer and override some forwarding rules defaults, including the global access policy, the IP protocol, the IP version and ports.
 

modules/workstation-cluster/README.md

@@ -74,7 +74,7 @@ module "workstation-cluster" {
 
 ## Custom image
 
-Example showing how to create a cluster with publicly accesible workstation that run a custom image.
+Example showing how to create a cluster with publicly accessible workstation that run a custom image.
 
 ```hcl
 module "workstation-cluster" {

tests/fixtures.py

@@ -392,7 +392,7 @@ def e2e_tfvars_path():
   Otherwise, create a unique test environment (in case of multiple workers - as many environments as
   there are workers), that will be injected into each example test instead of `tests/examples/variables.tf`.
 
-  Returns path to tfvars file that contains information about envrionment to use for the tests.
+  Returns path to tfvars file that contains information about environment to use for the tests.
   """
   if tfvars_path := os.environ.get('TFTEST_E2E_TFVARS_PATH'):
     # no need to set up the project