Getting started-edify : Changes only to Overview / Getting-Started files (#2310)

* Update index.md

For getting-started-edify folder

* Update create-account.md

For getting started folder

* Update invite-team.md

* Update link-github-id.md

* Update docs/2.0/docs/overview/getting-started/index.md

* Update docs/2.0/docs/overview/getting-started/invite-team.md

* Update docs/2.0/docs/overview/getting-started/invite-team.md

* Update docs/2.0/docs/overview/getting-started/link-github-id.md

Co-authored-by: Yousif Akbar <[email protected]>

* fix KodeKloud

---------

Co-authored-by: Zach Goldberg <[email protected]>
Co-authored-by: Yousif Akbar <[email protected]>
Co-authored-by: Zach Goldberg <[email protected]>

Author: 3 people

custom-dictionary.txt

@@ -46,4 +46,5 @@ dlist
 DEPENDENCYID
 MTTR
 terrapatch
-Terrapatch
+Terrapatch
+KodeKloud

docs/2.0/docs/overview/getting-started/create-account.md

@@ -2,35 +2,36 @@
 
 ## 1. Accept your invitation
 
-You’ll receive an invitation email from `[email protected]` prompting you to sign in and set up your account. Click on the button in the invitation email.
+You’ll receive an email invitation from `[email protected]` prompting you to sign in and set up your account. Click the button in the invitation email.
 
-After reviewing the privacy policy and website terms, check the box to indicate your agreement. You can then proceed to accept your invitation using only the email address to which the invite was sent. If it's a Google email, click **Continue With Google**; otherwise, enter your name and click **Continue with Email**.
+After reviewing the privacy policy and website terms, check the box to indicate your agreement. Proceed to accept your invitation using the email address to which the invitation was sent. If it's a Google email, click **Continue With Google**; otherwise, enter your name and click **Continue with Email**.
 
 :::note
 
-The *first* invitation email sent following the purchase of a new subscription may be forwarded to the appropriate admin for the team.
+The *first* invitation email sent after purchasing a new subscription may be forwarded to the appropriate team admin.
 
 :::
 
 ## 2. Confirm your email address
 
-If you continue with email, you’ll be prompted to check your inbox. Gruntwork uses a passwordless email authentication flow each time you sign in. Just click the link in that email to finish signing in.
+If you choose to continue with email, you’ll be prompted to check your inbox. Gruntwork uses a passwordless email authentication flow for every login. Click the link in the email to complete the sign-in process.
 
-If you receive an error indicating that the link has expired immediately after attempting to sign in, it's likely due to software such as Microsoft SafeLink™ or Mimecast, which pre-processes links for security, thus invalidating it for using to sign in. Request a new sign-in link, then refer to the **Trouble Signing In** section at the bottom of the email. Select the displayed link text, then copy and paste it into your browser to sign in.
+If you encounter an error stating that the link has expired, it may be due to security software such as Microsoft SafeLink™ or Mimecast, which pre-processes links and invalidates them. Request a new sign-in link, then refer to the **Trouble Signing In** section at the bottom of the email. Copy and paste the displayed link text directly into your browser to sign in.
 
 :::note
 
-For security, sign in emails expire after 10 minutes. You can enter your email at [app.gruntwork.io](https://app.gruntwork.io) to receive a new sign in link at any time.
+For security, sign-in links expire after 10 minutes. You can request a new sign-in link anytime by entering your email at [app.gruntwork.io](https://app.gruntwork.io).
 
 :::
 
 
 ## 3. Provide account details
 
-If you are the admin for your organization, you'll be prompted to confirm details including your company address and phone number, as well as a billing email. Provide the required information and click **Continue** to finish signing in.
+If you are the admin for your organization, you’ll be prompted to confirm details such as your company address, phone number, and billing email. Provide the required information and click **Continue** to complete the sign-in process.
 
-## Related Knowledge Base Discussions
+## Related knowledge base discussions
 
 - [Invitation to the Developer Portal not received](https://github.com/orgs/gruntwork-io/discussions/716)
 - [Trouble logging into the Portal with email](https://github.com/orgs/gruntwork-io/discussions/395)
 - [How can the email associated with an account be changed?](https://github.com/orgs/gruntwork-io/discussions/714)
+

docs/2.0/docs/overview/getting-started/index.md

@@ -1,34 +1,40 @@
 # Setting up DevOps Foundations & Components
 import PersistentCheckbox from '/src/components/PersistentCheckbox';
 
-### Step 1: [Activate Your Gruntwork Account](/2.0/docs/overview/getting-started/create-account)
+### Step 1: [Activate your Gruntwork account](/2.0/docs/overview/getting-started/create-account)
 
-Set up your Gruntwork account and invite your teammates to gain access to Gruntwork resources.
+Create your Gruntwork account and invite your team members to access Gruntwork resources.
 
 <PersistentCheckbox id="install-df-1" label="Gruntwork Account Ready" />
 
-### Step 2: [Set Up a Landing Zone](/2.0/docs/pipelines/installation/prerequisites/awslandingzone)
+### Step 2: [Set up a Landing Zone](/2.0/docs/pipelines/installation/prerequisites/awslandingzone)
 
-Gruntwork's AWS Landing Zone walkthrough provides a best practice multi-account setup ready to use with DevOps Foundations.
+Follow Gruntwork's AWS Landing Zone walkthrough to implement a best-practice multi-account setup, ready for use with DevOps Foundations.
 
 <PersistentCheckbox id="install-df-2" label="AWS Landing Zone Ready" />
 
-### Step 3: [Configure Pipelines Authentication](/2.0/docs/pipelines/installation/authoverview)
+### Step 3: [Configure Pipelines authentication](/2.0/docs/pipelines/installation/authoverview)
+
+Set up authentication for Pipelines to enable secure automation of infrastructure changes.
 
 <PersistentCheckbox id="install-df-3" label="Pipelines Auth Configured" />
 
-### Step 4: [Create New Pipelines Repositories](/2.0/docs/pipelines/installation/addingnewrepo)
+### Step 4: [Create new Pipelines repositories](/2.0/docs/pipelines/installation/addingnewrepo)
 
-Or alternatively [Add Pipelines To An Existing Repository](/2.0/docs/pipelines/installation/addingexistingrepo).
+Alternatively, you can [add Pipelines to an existing repository](/2.0/docs/pipelines/installation/addingexistingrepo).
 
 <PersistentCheckbox id="install-df-4" label="Pipelines Repositories Ready" />
 
-### Step 5: [Configure Account Factory](/2.0/reference/accountfactory/configurations).
+### Step 5: [Configure Account Factory](/2.0/reference/accountfactory/configurations)
 
-As part of your Pipelines installation, you will now have Gruntwork Account Factory
+During the Pipelines setup process, configure Gruntwork Account Factory for AWS account management.
 
 <PersistentCheckbox id="install-df-5" label="Account Factory Configured" />
 
-### Step 6: Start Using DevOps Foundations
+### Step 6: Start using DevOps Foundations
 
-That's it! You're ready to [build with Gruntwork IaC Library](/2.0/docs/library/tutorials/deploying-your-first-gruntwork-module) automatically [plan and apply IaC changes with Pipelines](/2.0/docs/pipelines/guides/running-plan-apply), [vend new AWS Accounts with Account Factory](/2.0/docs/accountfactory/guides/vend-aws-account), and [keep your infrastructure up to date with Patcher](/2.0/docs/patcher/concepts/).
+You're all set! You can now:
+- [Build with the Gruntwork IaC Library](/2.0/docs/library/tutorials/deploying-your-first-gruntwork-module)
+- Automatically [plan and apply IaC changes with Pipelines](/2.0/docs/pipelines/guides/running-plan-apply)
+- [Vend new AWS accounts with Account Factory](/2.0/docs/accountfactory/guides/vend-aws-account)
+- [Keep your infrastructure up to date with Patcher](/2.0/docs/patcher/concepts/)

docs/2.0/docs/overview/getting-started/invite-team.md

@@ -1,46 +1,44 @@
 # Invite Your Team
 
-All members of your team with an admin role have the ability to manage team membership. The first admin will also be prompted to invite their team immediately after signing in for the first time.
-
+Team members with an admin role can manage team membership. The first admin will also be prompted to invite their team immediately after signing in for the first time.
 
 ## Inviting team members
 
-Invite team members to grant them access to the portal and all resources included in your Gruntwork Subscription.
+Invite team members to give them access to the portal and all resources included in your Gruntwork subscription.
 
 1. Navigate to the **[Team](https://app.gruntwork.io/team)** page of the Gruntwork Developer Portal.
-2. Click the **Invite** button. A new row will appear beneath the table of team members.
-3. Enter the email address of the person you’d like to invite.
-4. Select the appropriate role for this team member. All members get access to Gruntwork resources. Admins may additionally manage account information and team membership. (If you accidentally invite someone with the wrong role, you can change it even after the invite has been sent.)
+2. Click the **Invite** button. A new row will appear below the table of team members.
+3. Enter the email address of the person you wish to invite.
+4. Select the appropriate role for the team member. All members can access Gruntwork resources. Admins can additionally manage account information and team membership. (If you assign the wrong role, you can change it even after the invite has been sent.)
 5. Press `ENTER` or click the arrow at the right of the row.
 
-This will send an invitation to the provided email address. You can continue inviting additional team members by repeating steps 3–5. If any errors are encountered, an error icon will appear at the right of the row, and you’ll have the opportunity to edit the email and retry as needed.
+This will send an invitation to the provided email address. To invite additional team members, repeat steps 3–5. If an error occurs, an error icon will appear at the right of the row, allowing you to edit the email and retry.
 
-## Changing User Roles
+## Changing user roles
 
-Admins can change the role of any team member at any time, including those who haven’t yet accepted their invitation. As such, it’s possible to make a correction if you invited a team member with the wrong role.
+Admins can change the role of any team member at any time, including those who haven’t accepted their invitation. This allows you to correct any mistakes made during the invitation process.
 
-1. Locate the team member in the table who’s role you wish to change.
+1. Locate the team member in the table whose role you wish to change.
 2. Click on their current role.
 3. Select a new role.
 
-This change will take effect immediately. Any team members who have accepted their invitation will receive an email notifying them of this change.
+The change will take effect immediately. Team members who have already accepted their invitation will receive an email notification about the role update.
 
 ## Removing team members
 
-Remove team members to free up licenses when they no longer require access to Gruntwork resources. You can also revoke outstanding invitations with the same steps. Once removed from the team, the user will no longer be able to sign in to the Gruntwork Developer portal, nor access Gruntwork resources such as the IaC Library or Teachable video training courses.
+Remove team members to free up licenses when they no longer require access to Gruntwork resources. You can also revoke pending invitations using the same process. Once removed, the user will no longer be able to sign in to the Gruntwork Developer Portal or access resources such as the IaC Library or KodeKloud video training courses.
 
 1. Locate the team member you wish to remove in the table.
-2. Hover over the row, then click the red remove button at the right of the row.
-3. Confirm that you wish to remove them from the team and revoke their access.
-
-This change will take effect immediately. Any team members who have accepted their invitation will receive an email notifying them that they have been removed from the team, and will no longer be able to sign in or access Gruntwork resources.
+2. Hover over the row and click the red remove button on the right.
+3. Confirm the removal to revoke their access.
 
+The change will take effect immediately. If the removed team member has already accepted their invitation, they will receive an email notifying them that their access has been revoked.
 
 ## Requesting additional licenses
 
-The number of licenses available depends on the level of your subscription. You can see the total number of licenses as well as the number remaining at the top of the [Team](https://app.gruntwork.io/team) page. If you need to invite more team members than your current license limit allows, you may request additional licenses, which are billed at a standard monthly rate. To do so, contact [email protected].
+The number of licenses available depends on your subscription level. You can view the total and remaining licenses at the top of the [Team](https://app.gruntwork.io/team) page. If you need to invite more team members than your current license limit allows, you can request additional licenses at a standard monthly rate. Contact [email protected] to request more licenses.
 
-## Related Knowledge Base Discussions
+## Related knowledge base discussions
 
 - [Invitation to the Developer Portal not received](https://github.com/orgs/gruntwork-io/discussions/716)
 - [Trouble logging into the Portal with email](https://github.com/orgs/gruntwork-io/discussions/395)

docs/2.0/docs/overview/getting-started/link-github-id.md

@@ -2,33 +2,34 @@
 pagination_next: 2.0/docs/overview/getting-started/index
 ---
 
-# Link Your GitHub Account
+# Link Your GitHub account
 
-Gruntwork provides all code included in your subscription through GitHub. You need to link a GitHub ID to your Gruntwork Developer Portal account in order to access the IaC Library on GitHub. Follow the steps below to link your GitHub ID.
+Gruntwork provides all code included in your subscription through GitHub. To access the IaC Library on GitHub, you must link your GitHub ID to your Gruntwork Developer Portal account. Follow these steps to complete the process:
 
-1. First, sign in to the [Gruntwork Developer Portal](https://app.gruntwork.io).
-2. Click the **Link my GitHub Account** button in the notice at the top of the home page, or the corresponding button located in your [Profile Settings](https://app.gruntwork.io/settings/profile).
-3. Sign in to your GitHub account, then click the **Authorize** button to confirm the connection.
-4. After being redirected back to the Gruntwork Developer Portal, click the **Accept My Invite** button. This will take you to GitHub again, where you can accept an invitation to join the Gruntwork organization. (You can ignore the corresponding invite email you receive from GitHub.)
-5. Click **Join Gruntwork** to accept the invitation and access the IaC Library.
+1. Sign in to the [Gruntwork Developer Portal](https://app.gruntwork.io).
+2. Click the **Link my GitHub Account** button, either in the notice at the top of the home page or in your [Profile Settings](https://app.gruntwork.io/settings/profile).
+3. Sign in to your GitHub account and click the **Authorize** button to confirm the connection.
+4. After being redirected back to the Gruntwork Developer Portal, click the **Accept My Invite** button. This will return you to GitHub, where you can accept an invitation to join the Gruntwork organization. (You can disregard the corresponding email invitation from GitHub.)
+5. Click **Join Gruntwork** to accept the invitation and gain access to the IaC Library.
 
 :::info
 
-Once you’ve linked your account, the notice on the home page will disappear and you’ll find your GitHub ID recorded in your [Profile Settings](https://app.gruntwork.io/settings/profile). Going forward, you’ll have access to all private repositories included in your subscription. If you haven’t done so yet, we strongly recommend [adding an SSH key](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) to your GitHub account. An SSH key is required to access the Gruntwork IaC library without adding a password in your Terraform code.
+Once your account is linked, the notice on the home page will disappear, and your GitHub ID will be recorded in your [Profile Settings](https://app.gruntwork.io/settings/profile). You will then have access to all private repositories included in your subscription. If you haven’t done so already, we strongly recommend [adding an SSH key](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) to your GitHub account. This is required to access the Gruntwork IaC library without entering a password in your OpenTofu/Terraform code.
 
 :::
 
 :::note
 
-[GitHub has begun requiring](https://github.blog/2023-03-09-raising-the-bar-for-software-security-github-2fa-begins-march-13) users to enable two-factor authentication (2FA). If you haven't already done so, we recommend [enabling 2FA](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication) for your account and any machine users. For more information on the benefits of two-factor authentication and how this change may impact you, please take a look at our [Knowledge Base article](https://github.com/orgs/gruntwork-io/discussions/764).
+[GitHub now requires](https://github.blog/2023-03-09-raising-the-bar-for-software-security-github-2fa-begins-march-13) users to enable two-factor authentication (2FA). If you haven’t already, we recommend [enabling 2FA](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication) for your account and any machine users. For more details on 2FA benefits and potential impacts, see our [Knowledge Base article](https://github.com/orgs/gruntwork-io/discussions/764).
 
 :::
 
-## Next Steps
 
-Now that you've completed setting up your Gruntwork account, return to the [DevOps Foundations Getting Started Checklist](/2.0/docs/overview/getting-started/index.md) to continue setting up your DevOps Foundations.
+## Next steps
 
-## Related Knowledge Base Discussions
+Now that you’ve linked your GitHub account, return to the [DevOps Foundations Getting Started Checklist](/2.0/docs/overview/getting-started/index.md) to continue setting up your DevOps Foundations.
+
+## Related knowledge base discussions
 
 - [I have linked my GitHub Account but do not have code access](https://github.com/orgs/gruntwork-io/discussions/715)
 - [How can I change my GitHub account (unlink/link)?](https://github.com/orgs/gruntwork-io/discussions/713)