docs: fix multiple typos in Actions, Packages, and Billing (#43044)

Co-authored-by: umutKaracelebi <umutkaracelebi@gmail.com>

Author: umutKaracelebi

content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-with-reusable-workflows.md

@@ -38,7 +38,7 @@ When combined with OpenID Connect (OIDC), reusable workflows let you enforce con
 
 ## How the token works with reusable workflows
 
-During a workflow run, {% data variables.product.prodname_dotcom %}'s OIDC provider presents a OIDC token to the cloud provider which contains information about the job. If that job is part of a reusable workflow, the token will include the standard claims that contain information about the calling workflow, and will also include a custom claim called `job_workflow_ref` that contains information about the called workflow.
+During a workflow run, {% data variables.product.prodname_dotcom %}'s OIDC provider presents an OIDC token to the cloud provider which contains information about the job. If that job is part of a reusable workflow, the token will include the standard claims that contain information about the calling workflow, and will also include a custom claim called `job_workflow_ref` that contains information about the called workflow.
 
 For example, the following OIDC token is for a job that was part of a called workflow. The `workflow`, `ref`, and other attributes describe the caller workflow, while `job_workflow_ref` refers to the called workflow:
 

content/actions/how-tos/write-workflows/choose-what-workflows-do/use-variables.md

@@ -122,7 +122,7 @@ In addition to runner environment variables, {% data variables.product.prodname_
 
 The `run` steps in a workflow, or in a referenced action, are processed by a runner. As a result, you can use runner environment variables here, using the appropriate syntax for the shell you are using on the runner - for example, `$NAME` for the bash shell on a Linux runner, or `$env:NAME` for PowerShell on a Windows runner. In most cases you can also use contexts, with the syntax {% raw %}`${{ CONTEXT.PROPERTY }}`{% endraw %}, to access the same value. The difference is that the context will be interpolated and replaced by a string before the job is sent to a runner.
 
-However, you cannot use runner environment variables in parts of a workflow that are processed by {% data variables.product.prodname_actions %} and are not sent to the runner. Instead, you must use contexts. For example, an `if` conditional, which determines whether a job or step is sent to the runner, is always processed by {% data variables.product.prodname_actions %}. You must therefore use a context in an `if` conditional statement to access the value of an variable.
+However, you cannot use runner environment variables in parts of a workflow that are processed by {% data variables.product.prodname_actions %} and are not sent to the runner. Instead, you must use contexts. For example, an `if` conditional, which determines whether a job or step is sent to the runner, is always processed by {% data variables.product.prodname_actions %}. You must therefore use a context in an `if` conditional statement to access the value of a variable.
 
 {% raw %}
 

content/billing/concepts/product-billing/github-packages.md

@@ -86,7 +86,7 @@ If your account does not have a valid payment method on file, usage is blocked o
 
 You pay for any additional use above your quota using the payment method set up for your {% data variables.product.github %} account. See [AUTOTITLE](/billing/how-tos/set-up-payment/manage-payment-info).
 
-Data transfer is billed for each GB of data transfered. Storage is billed by calculating an hourly usage rate.
+Data transfer is billed for each GB of data transferred. Storage is billed by calculating an hourly usage rate.
 
 * {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %}
 * To view your current storage and bandwidth, see [AUTOTITLE](/billing/managing-billing-for-your-products/viewing-your-product-usage).

content/packages/learn-github-packages/introduction-to-github-packages.md

@@ -55,7 +55,7 @@ Unlike {% data variables.product.prodname_registry %}, the {% data variables.pro
 
 Your organization may benefit from using the {% data variables.product.virtual_registry %} either:
 
-* **Alongside** {% data variables.product.prodname_registry %}, as an complementary view focused on the compliance and security aspects of package consumption
+* **Alongside** {% data variables.product.prodname_registry %}, as a complementary view focused on the compliance and security aspects of package consumption
 * **As an alternative to** {% data variables.product.prodname_registry %}, allowing you to store your packages on an external registry of your choice while maintaining visibility of the packages on {% data variables.product.github %}
 
 For more information, see [AUTOTITLE](/code-security/concepts/supply-chain-security/linked-artifacts).