Apply fixes (#3492)

helinanever · web-flow · commit 2974c31ae352 · 2026-06-05T11:19:28.000+03:00
diff --git a/content/flutter-code-signing/android-code-signing.md b/content/flutter-code-signing/android-code-signing.md
@@ -5,7 +5,7 @@ weight: 3
 aliases: /code-signing/android-code-signing
 ---
 
-Code signing is required for distributing your Android app to the Google Play store. It enables to identify who developed the app and ensure that all updates to the app come from you.
+Code signing is required for distributing your Android app to the Google Play store. It enables you to identify who developed the app and ensure that all updates to the app come from you.
 
 {{<notebox>}}
 **Note:** This guide only applies to workflows configured with the **Flutter workflow editor**. If your workflow is configured with **codemagic.yaml** please go to [Signing Android apps using codemagic.yaml](../code-signing-yaml/signing-android).
diff --git a/content/flutter-code-signing/ios-code-signing.md b/content/flutter-code-signing/ios-code-signing.md
@@ -7,7 +7,7 @@ weight: 1
 aliases: /code-signing/ios-code-signing
 ---
 
-Code signing is required by Apple for integrating app services, installing your iOS app on real devices, and for uploading it to App Store Connect so that it can be distributed through TestFlight or App Store. It enables to identify who developed the app and ensure that all the changes to the app come from you or your team.
+Code signing is required by Apple for integrating app services, installing your iOS app on real devices, and for uploading it to App Store Connect so that it can be distributed through TestFlight or App Store. It enables you to identify who developed the app and ensure that all the changes to the app come from you or your team.
 
 To receive a signed `.ipa` file of your app on Codemagic, you need to set up code signing.
 
diff --git a/content/flutter-code-signing/macos-code-signing.md b/content/flutter-code-signing/macos-code-signing.md
@@ -5,7 +5,7 @@ weight: 2
 aliases: /code-signing/macos-code-signing
 ---
 
-Code signing is required by Apple for integrating app services, installing your macOS app on another machine or uploading it to distribute it through the Mac App Store or outside of Mac App Store. It enables to identify who developed the app and ensure that all the changes to the app come from you or your team.
+Code signing is required by Apple for integrating app services, installing your macOS app on another machine or uploading it to distribute it through the Mac App Store or outside of Mac App Store. It enables you to identify who developed the app and ensure that all the changes to the app come from you or your team.
 
 To create an application package that can be published to Mac App Store on Codemagic, you need to set up code signing.
 
diff --git a/content/flutter-distributing/publishing-to-codemagic-static-pages.md b/content/flutter-distributing/publishing-to-codemagic-static-pages.md
@@ -10,7 +10,7 @@ aliases:
 You can publish your web app to a custom subdomain of `codemagic.app` for easy access.
 
 {{<notebox>}}
-⚠️ **Note**: This feature is intended for **testing purposes only**. Production apps should be deployed to prodcution-grade web hosting services such as Firebase Hosting or Cloudflare pages.
+⚠️ **Note**: This feature is intended for **testing purposes only**. Production apps should be deployed to production-grade web hosting services such as Firebase Hosting or Cloudflare pages.
 {{</notebox>}}
 
 1. Go to **App settings > Distribution > Codemagic Static Pages** to configure publishing to Codemagic Static Pages.
diff --git a/content/flutter-testing/ios-provisioning.md b/content/flutter-testing/ios-provisioning.md
@@ -29,7 +29,7 @@ You can also check the [Register Devices](https://help.apple.com/developer-accou
 To add devices to an existing group, find the group in the **Tester groups** section and click **Add new devices**. 
 
 {{<notebox>}}
-**Note:** It is important to choose the actual bundle identifier when building an not use any XC Wildcards. Otherwise, the tester group will be unable to install the app and will get the error **_"This app cannot be installed because its integrity could not be verified_**"
+**Note:** It is important to choose the actual bundle identifier when building, and not use any XC Wildcards. Otherwise, the tester group will be unable to install the app and will get the error **_"This app cannot be installed because its integrity could not be verified_**"
 {{</notebox>}}
 
 ## Device registration
diff --git a/content/getting-started/faq.md b/content/getting-started/faq.md
@@ -64,7 +64,7 @@ Most definitely. The annual subscription grants you 2 months of free usage for t
 ## What’s an Enterprise plan?
 The Enterprise plan offers the same superb quality service you have come to expect from Codemagic but enhanced with additional customization options. This plan is recommended if you need to go through a security compliance process, vendor registration or have special requirements such as an NDA, DPA, dedicated hosts, custom base images, or other account management services. Enterprise customers are also able to authenticate using SSO.
 
-## How's a dedicated host different from shared hosts
+## How's a dedicated host different from shared hosts?
 
 The common pool operates on shared hardware, where the physical machine resources are shared between two virtual machines. During peak periods, up to two VMs may be deployed on a single host. 
 
diff --git a/content/getting-started/teams.md b/content/getting-started/teams.md
@@ -35,7 +35,7 @@ To add new applications to a team, click **Add application** on the Apps page an
 {{<notebox>}}
 **Notes on transferring apps to team:** 
 * Please review the repository settings and team integrations to ensure that your setup is intact and the repository is still accessible after the transfer. Read more about configuring repository access in [team integrations](#managing-team-integrations).
-* As Personal accounts and team accounts are two different teams/accounts, iOS and Android code signing identities are not transferred from personal accounts, so please re-adjust workflows that rely on these configurations. To continue working with iOS automatic code signing in the Workflow Editor, you need to re-add the App Store Connect API key (.p8) in your team settings as the API keys are not shared between accounts. Moreover, none of the personal account integrations from your personal account settings > **Integrations** is migrated.
+* As Personal accounts and team accounts are two different teams/accounts, iOS and Android code signing identities are not transferred from personal accounts, so please re-adjust workflows that rely on these configurations. To continue working with iOS automatic code signing in the Workflow Editor, you need to re-add the App Store Connect API key (.p8) in your team settings as the API keys are not shared between accounts. Moreover, none of the personal account integrations from your personal account settings > **Integrations** are migrated.
 * If you used code signing identities on your personal account, please review any setup related to code signing identities.
 * Once an application has been transferred to a team, it cannot be transferred back to the personal account or to other teams.
 {{</notebox>}}
diff --git a/content/integrations/appknox-integration.md b/content/integrations/appknox-integration.md
@@ -25,7 +25,7 @@ Signing up with Appknox [here](https://www.appknox.com/) is required to be able
       - appknox_credentials
 {{< /highlight >}}
 
-8. Adding the following scripts in **codemagic.yaml** will allow you to start the security scanning process in the the Appknox environment:
+8. Adding the following scripts in **codemagic.yaml** will allow you to start the security scanning process in the Appknox environment:
 
 
 {{< highlight yaml "style=paraiso-dark">}}
diff --git a/content/integrations/codecov-integration.md b/content/integrations/codecov-integration.md
@@ -15,7 +15,7 @@ A sample project that shows how to configure Codecov integration is available in
 1. In order to get a dedicated Codecov token, signing up is required. You can sign up for free [here](https://about.codecov.io/).
 1. Open your Codemagic app settings, and go to the **Environment variables** tab.
 2. Enter the desired **_Variable name_**, e.g. `CODECOV_TOKEN`.
-3. Copy and paste the Capgo token string as **_Variable value_**.
+3. Copy and paste the Codecov token string as **_Variable value_**.
 4. Enter the variable group name, e.g. **_codecov_credentials_**. Click the button to create the group.
 5. Make sure the **Secret** option is selected.
 6. Click the **Add** button to add the variable.
diff --git a/content/integrations/dcm-integration.md b/content/integrations/dcm-integration.md
@@ -14,7 +14,7 @@ To get started with [Dart Code Metrics](https://dcm.dev/), you need an API key a
 2. Open your Codemagic app settings, and go to the **Environment variables** tab.
 3. Enter the desired **_Variable name_**, e.g. `DCM_KEY`.
 4. Copy and paste the API key string as **_Variable value_**.
-5. Enter the variable group name, e.g. **_dcm_credntials_**. Click the button to create the group.
+5. Enter the variable group name, e.g. **_dcm_credentials_**. Click the button to create the group.
 6. Make sure the **Secret** option is selected.
 7. Click the **Add** button to add the variable.
 8. Repeat the above process for `DCM_EMAIL_ID`.
diff --git a/content/integrations/jenkins-integration.md b/content/integrations/jenkins-integration.md
@@ -19,7 +19,7 @@ The Application ID uniquely identifies your app in Codemagic API calls.
 2. Look at the app URL: https://codemagic.io/app/xxxxxxxxxxxxxxxxxxxxxxxx
 3. Copy the UUID at the end - this is your `AppID`.
 
-## Find you Workflow name
+## Find your Workflow name
 The Workflow name specifies which workflow to trigger.
 1. Navigate to your codemagic.yaml file (in Codemagic or in your repository)
 2. Copy the name of the workflow (e.g., `sample-workflow`)
diff --git a/content/integrations/katalon-integration.md b/content/integrations/katalon-integration.md
@@ -11,7 +11,7 @@ A sample project that shows how to configure Katalon integration is available in
 
 ## Configure Katalon access
 
-In order to create a project and retrive API key that are used when uploading test to the Katalon testing environment, you need to [sign up](https://katalon.com/) with Katalon.
+In order to create a project and retrieve the API key that is used when uploading tests to the Katalon testing environment, you need to [sign up](https://katalon.com/) with Katalon.
 
 1. Open your Codemagic app settings, and go to the **Environment variables** tab.
 2. Enter the desired **_Variable name_**, e.g. `KATALON_API_KEY`.
diff --git a/content/integrations/kobiton-integration.md b/content/integrations/kobiton-integration.md
@@ -91,7 +91,7 @@ Alternatively, use an [online tool](https://mixedanalytics.com/knowledge-base/ap
 {{< /tabpane >}}
 
 
-These capabitlies will allow Kobiton to detect which platform you want to execute your test scripts with. Each device specific capabilities for Java can be found in the **Kobiton devices list** by clicking **device settings** and then **Automation Settings**.
+These capabilities will allow Kobiton to detect which platform you want to execute your test scripts with. Each device specific capabilities for Java can be found in the **Kobiton devices list** by clicking **device settings** and then **Automation Settings**.
 
 
 ## Upload apps to Kobiton
diff --git a/content/integrations/lambdatest-integration.md b/content/integrations/lambdatest-integration.md
@@ -99,7 +99,7 @@ In order to see your tests being uploaded to the **App Automation**, tests need
 {{< /tabpane >}}
 
 
-These capabitlies will allow **LambdaTest** to detect which platform you want to you execute your test scripts with. In these capabilities, the main part is **app URL** which is generated in the response of the cURL request:
+These capabilities will allow **LambdaTest** to detect which platform you want to you execute your test scripts with. In these capabilities, the main part is **app URL** which is generated in the response of the cURL request:
 
 {{< highlight bash "style=paraiso-dark">}}
 
diff --git a/content/integrations/rock-integration.md b/content/integrations/rock-integration.md
@@ -130,7 +130,7 @@ When the `ios_signing` block references these by name in `codemagic.yaml`, Codem
 
 ### App Store Connect API Key
 In the Codemagic UI, go to **Teams → your team → Team integrations → Developer Portal** and click **Connect**. Upload your .p8 API key file and provide the associated Key ID and Issuer ID. Give the integration a name, for example `app_store_connect_key`.
-Once connected, reference it in your workflow with the integrations: block — no API key environment variables are needed in the 
+Once connected, reference it in your workflow with the integrations: block — no API key environment variables are needed in the workflow.
 
 {{< highlight yaml "style=paraiso-dark">}}
   integrations:
diff --git a/content/knowledge-codemagic/codemagic-cli-tools.md b/content/knowledge-codemagic/codemagic-cli-tools.md
@@ -8,7 +8,7 @@ aliases:
     - /cli/codemagic-cli-tools
 ---
 
-[codemagic-cli-tools](https://pypi.org/project/codemagic-cli-tools/) is a set of tools to simplify builds at Codemagic. They can be installed with via pip and run locally.
+[codemagic-cli-tools](https://pypi.org/project/codemagic-cli-tools/) is a set of tools to simplify builds at Codemagic. They can be installed via pip and run locally.
 {{< highlight bash "style=paraiso-dark">}}
   pip3 install codemagic-cli-tools
 {{< /highlight >}}
diff --git a/content/knowledge-codemagic/flutter-screenshots-stores.md b/content/knowledge-codemagic/flutter-screenshots-stores.md
@@ -268,7 +268,7 @@ itc_team_id("123456789") # App Store Connect Team ID
 team_id("123A4P567S") # Developer Portal Team ID
 {{< /highlight >}}
 
-- In order to locally get all the current screenshots and metadata with the right files and folders , run:
+- In order to locally get all the current screenshots and metadata with the right files and folders, run:
    `sudo fastlane deliver init --use_live_version true`.
    Here again, you might need to change the owners of the generated files as explained above.
 - Finally, if your app does not use encryption, in your `Info.plist` file, add the `ITSAppUsesNonExemptEncryption` key with `false` for its value.
diff --git a/content/knowledge-firebase/load-firebase-configuration.md b/content/knowledge-firebase/load-firebase-configuration.md
@@ -9,7 +9,7 @@ aliases:
 
 Instead of committing the Firebase configuration files to your repository, you can upload them to Codemagic as **environment variables** and reference them in a custom script.
 
- Save the **contents** of Firebase config files as environment variables, e.g. `ANDROID_FIREBASE_SECRET` and `IOS_FIREBASE_SECRET` in Codemagic UI (either in Application or Team variables) and select **Secret**. 
+ Save the **contents** of Firebase config files as environment variables, e.g. `ANDROID_FIREBASE_SECRET` and `IOS_FIREBASE_SECRET` in the Codemagic UI (either in Application or Team variables) and select **Secret**. 
 
 1. Open your Codemagic app settings, and go to the **Environment variables** tab.
 2. Enter the desired **_Variable name_**, e.g. `ANDROID_FIREBASE_SECRET` or `IOS_FIREBASE_SECRET`.
diff --git a/content/knowledge-git/plasticscm-sync-with-git.md b/content/knowledge-git/plasticscm-sync-with-git.md
@@ -6,7 +6,7 @@ aliases:
   - /knowledge-base/plasticscm-sync-with-git
 ---
 
-[Plastic SCM](https://www.plasticscm.com/) is a full-featured DVCS (Distributed Version Control Software)which also supports the Git network protocol.
+[Plastic SCM](https://www.plasticscm.com/) is a full-featured DVCS (Distributed Version Control Software) which also supports the Git network protocol.
 Plastic SCM can push and pull changes directly to any remote Git server. This is because Plastic supports the `https://` and `git://` protocols for pushing and pulling changesets.
 
 This feature immediately turns Plastic SCM into a DVCS fully compatible with Git. The advantage of this is that you can use Plastic or Git on your workstation and still participate in Git projects (GitHub, CodePlex, and many more). Check out the official [GitSync documentation](https://www.plasticscm.com/documentation/gitsync/plastic-scm-version-control-gitsync-guide).
diff --git a/content/knowledge-others/install-unity-version.md b/content/knowledge-others/install-unity-version.md
@@ -77,7 +77,7 @@ If you can't find your desired Unity version in the list, please contact us via
 **Notes:**
 - These versions are the `Unity Editor (macOS x86_64)`, and have only the `macOS`, `Android`, and `iOS` modules.
 - Mac machines with Apple silicon support Unity built for `x86_64` architecture.
-- If your app requires additional modules then you need to install it using [Unity Hub CLI](./-others/install-unity-version/#unity-installation-script) like this: `/Applications/Unity\ Hub.app/Contents/MacOS/Unity\ Hub -- --headless install-modules --version <UNITY_VERSION> -m windows-mono`, this will install the windows modules for the specified` <UNITY_VERSION>`.
+- If your app requires additional modules then you need to install them using [Unity Hub CLI](./-others/install-unity-version/#unity-installation-script) like this: `/Applications/Unity\ Hub.app/Contents/MacOS/Unity\ Hub -- --headless install-modules --version <UNITY_VERSION> -m windows-mono`, this will install the windows modules for the specified` <UNITY_VERSION>`.
 {{</notebox>}}
 
 ## Download and install from Unity Hub
diff --git a/content/knowledge-others/script-to-create-env-file.md b/content/knowledge-others/script-to-create-env-file.md
@@ -23,7 +23,7 @@ NOTE: using `>>` after the first line appends lines to the file
 
 The variables with $ in the above script can be imported from Codemagic UI. For more details, refer to this [document](../yaml-basic-configuration/using-environment-variables/).
 
-`For Windows`, Powershell requires a different command for this case:
+`For Windows`, PowerShell requires a different command for this case:
 
 {{< highlight powershell "style=rrt">}}
 cmd.exe /c "echo "MY_VAR=$env:VAR_NAME" > .env"
diff --git a/content/rn-codepush/releasing-updates.md b/content/rn-codepush/releasing-updates.md
@@ -17,7 +17,7 @@ CodePush updates are not managed through the Codemagic UI. All releases, promoti
 
 ## Overview
 
-After integrating the CodePush SDK into your React Native app as explained in the [previous sectio](http://localhost:1313/rn-codepush/setup/#add-codepush-to-a-react-native-app)n, you can ship updates without rebuilding or resubmitting your app to the App Store or Google Play.
+After integrating the CodePush SDK into your React Native app as explained in the [previous section](http://localhost:1313/rn-codepush/setup/#add-codepush-to-a-react-native-app), you can ship updates without rebuilding or resubmitting your app to the App Store or Google Play.
 
 CodePush delivers:
 * Updated JavaScript bundles
diff --git a/content/rn-codepush/setup.md b/content/rn-codepush/setup.md
@@ -282,7 +282,7 @@ At the end, your `sourceURLForBridge` method should look like this:
 }
 {{< /highlight >}}
 
-**Swift** :If your project is using `Swift` based configuration, then follow the steps below:
+**Swift**: If your project is using `Swift` based configuration, then follow the steps below:
 
 1. Navigate to your iOS project and open the `AppDelegate.swift` file
 2. Add the following import at the top of the file:
diff --git a/content/yaml-code-signing/signing-ios.md b/content/yaml-code-signing/signing-ios.md
@@ -75,7 +75,7 @@ When defining the bundle identifier `com.example.id`, Codemagic will fetch any u
 
 ### Fetching specific files by reference names
 
-For a more advanced configuration, it is possible to pick out specific uploaded profiles and certificates for Codemagic to fetch during the build. To do so, list the references of the uploaded files under the `provisioning_profiles` and `certificates` fields, respectively. Note than when fetching individual files, the fields `distribution_type` and `bundle_identifier` are not allowed.
+For a more advanced configuration, it is possible to pick out specific uploaded profiles and certificates for Codemagic to fetch during the build. To do so, list the references of the uploaded files under the `provisioning_profiles` and `certificates` fields, respectively. Note that when fetching individual files, the fields `distribution_type` and `bundle_identifier` are not allowed.
 
 Steps `Initialize keychain` & `Add certificates to keychain` scripts are not required as those are automatically fetched during the build process.
 
