Minor fixes

docs/pages/tutorial/eas/android-production-build.mdx

@@ -299,7 +299,7 @@ For subsequent releases in future, we can streamline the process by combining bu
     <>
       We successfully created a production-ready Android build, discussed manual and automated
       uploading to Google Play Store using <CODE>eas submit</CODE>, and automated the release
-      process with the <CODE>--auto-submit</CODE> flag.
+      process with the <CODE>--auto-submit</CODE>.
     </>
   }
   nextChapterDescription="

docs/pages/tutorial/eas/configure-development-build.mdx

@@ -17,7 +17,7 @@ In this chapter, we'll set up and configure a development build with EAS for our
 
 Let's start by learning about what are development builds and why we need them.
 
-A [development build](/develop/development-builds/introduction/) is a debug version of our project. It is optimized for quick iterations when creating an app.IT contains the [`expo-dev-client`](/versions/latest/sdk/dev-client/) library, which offers a robust and complete development environment. This setup allows us to integrate any native library or change code inside the [native directories](/workflow/overview/#android-and-ios-native-projects) as required.
+A [development build](/develop/development-builds/introduction/) is a debug version of our project. It is optimized for quick iterations when creating an app. It contains the [`expo-dev-client`](/versions/latest/sdk/dev-client/) library, which offers a robust and complete development environment. This setup allows us to integrate any native library or change code inside the [native directories](/workflow/overview/#android-and-ios-native-projects) as required.
 
 ### Key highlights
 
@@ -41,7 +41,7 @@ To initialize our project for a development build, let's [`cd`](https://develope
 
 ### Start the development server
 
-Run the `npx expo start` to start the [development server](/get-started/create-a-project/#start-the-development-server):
+Run the `npx expo start` to start the [development server](/get-started/start-developing/#start-a-development-server):
 
 <Terminal cmd={['$ npx expo start']} />
 
@@ -80,7 +80,7 @@ To log in, run the following command:
 
 <Terminal cmd={['$ eas login']} />
 
-This command asks for our EAS email or username and password to complete the login.
+This command asks for our Expo account email or username and password to complete the login.
 
 ### Initialize and link the project to EAS
 
@@ -192,7 +192,7 @@ Currently, our focus is on the `development` profile, which includes the followi
   currentChapterIndex={0}
   name="EAS_TUTORIAL"
   summary="
-We successfully the EAS CLI to install, initialize, and configure our project, linking the project to EAS servers and preparing a development build."
+We successfully used the EAS CLI to initialize, and configure our project, link it to EAS servers, and prepare a development build."
   nextChapterDescription="In the next chapter, let's create a development build for Android, install it on a device and an emulator, and get it running with the development server."
   nextChapterTitle="Create and run a cloud build for Android"
   nextChapterLink="/tutorial/eas/android-development-build/"

docs/pages/tutorial/eas/internal-distribution-builds.mdx

@@ -182,7 +182,7 @@ Since we have already set up multiple app variants, we can see both the developm
 <ProgressTracker
   currentChapterIndex={5}
   name="EAS_TUTORIAL"
-  summary="We successfully created internal distribution builds for Android and iOS, used ad hoc provisioning for iOS, and installed multiple app variants using shareable links."
+  summary="We successfully created internal distribution builds for Android and iOS, used ad hoc provisioning for iOS, and installed multiple app variants on the same device."
   nextChapterDescription="In the next chapter, learn about developer-facing and user-facing app versions and how to manage them automatically."
   nextChapterTitle="Manage different app versions"
   nextChapterLink="/tutorial/eas/manage-app-versions/"

docs/pages/tutorial/eas/introduction.mdx

@@ -26,7 +26,7 @@ These topics will give us the foundation needed to use EAS effectively and to ap
 
 ## Prerequisites
 
-This tutorial is hands-on and designed to be completed in about two hours. You will need an existing Expo project to follow along. Options include:
+This tutorial is hands-on and designed to be completed in about two hours. You will need an existing Expo project to follow along and set it up locally on your machine. Options include:
 
 - Continuing with the Sticker Smash app from our previous tutorial. If new, download it from [GitHub](https://github.com/amandeepmittal/sticker-smash-expo-tutorial-app).
 - Starting a new project with [`npx create-expo-app`](/get-started/create-a-project/).

docs/pages/tutorial/eas/ios-development-build-for-devices.mdx

@@ -19,7 +19,7 @@ Development builds for iOS devices are generated in the **.ipa** format, which i
 Before we begin, ensure you have:
 
 - **Apple Developer Account:** This is required to access [necessary credentials](/app-signing/app-credentials/#ios) for signing our app, as each build needs to be signed to verify that the app comes from a trusted source. EAS Build helps manage these credentials.
-- **Developer Mode activated on iOS 16 and higher:** Installing development builds on your device requires Developer Mode to be enabled. If this is your first time or if it's currently disabled, see these instructions to [activate Developer Mode Developer Mode](/guides/ios-developer-mode/).
+- **Developer Mode activated on iOS 16 and higher:** Installing development builds on your device requires Developer Mode to be enabled. If this is your first time or if it's currently disabled, see these instructions to [activate Developer Mode](/guides/ios-developer-mode/).
 
 ## Provisioning profile
 

docs/pages/tutorial/eas/ios-production-build.mdx

@@ -163,7 +163,7 @@ For future releases, we can streamline the process by combining build creation a
     <>
       We successfully created a production-ready iOS build, discussed distribution using TestFlight
       and Apple App Store using <CODE>eas submit</CODE>, and automated the release process with the{' '}
-      <CODE>--auto-submit</CODE> flag.
+      <CODE>--auto-submit</CODE>.
     </>
   }
   nextChapterDescription="In the next chapter, learn how to use the EAS Update to send OTA updates and share previews with our team."

docs/pages/tutorial/eas/manage-app-versions.mdx

@@ -23,11 +23,15 @@ We can manually manage developer-facing values by setting them as `android.versi
 ```json app.config.js
 {
   "ios": {
+    /* @info */
     "buildNumber": "1"
+    /* @end */
     /* @hide ... */ /* @end */
   },
   "android": {
+    /* @info */
     "versionCode": "1"
+    /* @end */
   }
   /* @hide ... */ /* @end */
 }
@@ -51,13 +55,13 @@ In **eas.json**:
 {
   "cli": {
     /* @hide ... */ /* @end */
-    /* @info Add <CODE>appVersionSource</CODE> and set it to remote. */
+    /* @info Add <CODE>appVersionSource</CODE> and set it to <CODE>remote</CODE>. */
     "appVersionSource": "remote"
     /* @end */
   },
   "build": {
     "production": {
-      /* @info Set the autoIncrement property to true to automatically increment the versionCode or buildNumber */
+      /* @info Set the <CODE>autoIncrement</CODE> property to true to automatically increment the <CODE>versionCode</CODE> or <CODE>buildNumber</CODE>. */
       "autoIncrement": true
       /* @end */
     }
@@ -66,7 +70,7 @@ In **eas.json**:
 }
 ```
 
-When we create a new production build in the next two chapters, the `versionCode` for Android or `buildNumber` for iOS will increment automatically.
+When we create a new production build in the next two chapters, the `versionCode` for Android and `buildNumber` for iOS will increment automatically.
 
 ## Summary
 
@@ -75,9 +79,9 @@ When we create a new production build in the next two chapters, the `versionCode
   name="EAS_TUTORIAL"
   summary={
     <>
-      We successfully explored app versioning differences, addressed the importance of unique
+      We successfully explored app versioning differences, addressed the importance of unique app
       versions to prevent store rejections, and enabled automated version updates in{' '}
-      <strong>eas.json</strong> for production.
+      <strong>eas.json</strong> for production builds.
     </>
   }
   nextChapterDescription="In the next chapter, learn about the process of creating a production build for Android."

docs/pages/tutorial/eas/multiple-app-variants.mdx

@@ -178,9 +178,10 @@ Now, our development build will run on both Android and iOS, displaying the modi
   name="EAS_TUTORIAL"
   summary={
     <>
-      We successfully configured various build types, switched to <strong>app.config.js</strong> for
-      dynamic settings, added environment variables in <strong>eas.json</strong>, and started the
-      development server using a custom <strong>package.json</strong> script.
+      We successfully switched to <strong>app.config.js</strong> for dynamic settings, added
+      environment variables in <strong>eas.json</strong> to configure specific build profile, and
+      learned how to start the development server with a custom <strong>package.json</strong>{' '}
+      script.
     </>
   }
   nextChapterDescription="In the next chapter, learn about what are internal distribution builds, why we need them, and how to create them."

docs/pages/tutorial/eas/next-steps.mdx

@@ -65,7 +65,7 @@ But this is just the beginning. Here are some next steps to continue your journe
 <BoxLink
   title="eas.json schema"
   Icon={BookOpen02Icon}
-  description="See eas.json schema reference to learn more about available properties for EAS Build and EAS Submit to configure and override their default behavior from within your project."
+  description="See the complete schema reference to learn more about available properties for EAS Build and EAS Submit, and to configure and override their default behavior from within your project."
   href="/eas/json/"
 />
 

docs/pages/tutorial/eas/team-development.mdx

@@ -11,7 +11,7 @@ import { Collapsible } from '~/ui/components/Collapsible';
 import Video from '~/components/plugins/Video';
 import { ProgressTracker } from '~/ui/components/ProgressTracker';
 
-Updates generally fix small bugs and push small changes in between app store releases. They allow updating the non-native parts of our app, such as JavaScript code, styling, and images.
+Updates generally fix small bugs and push small changes in between app store releases. They allow updating the non-native parts of our example app, such as JavaScript code, styling, and images.
 
 In this chapter, we'll use [EAS Update](/eas-update/introduction/) to share changes with our team. This will help [us and our team quickly share previews](/review/overview/) of the change.
 
@@ -49,18 +49,24 @@ If a project doesn't use dynamic app config (uses **app.json** instead of **app.
   "build": {
     "development": {
       /* @hide ... */ /* @end */
+      /* @info */
       "channel": "development"
+      /* @end */
     },
     "ios-simulator": {
       /* @hide ... */ /* @end */
     },
     "preview": {
       /* @hide ... */ /* @end */
+      /* @info */
       "channel": "preview"
+      /* @end */
     },
     "production": {
       /* @hide ... */ /* @end */
+      /* @info */
       "channel": "production"
+      /* @end */
     }
   }
   /* @hide ... */ /* @end */
@@ -97,7 +103,7 @@ After the new version of the development build is created, make sure to install
 
 Let's modify our example app's JavaScript code. If you are not using [Sticker Smash app](/tutorial/eas/introduction/#prerequisites), you can modify any piece of your code to see the changes in the app.
 
-We'll modify the text of the first button in our app that says **Choose a photo** to **Select a photo**.
+We'll modify the text of the first button in our example app that says **Choose a photo** to **Select a photo**.
 
 ```jsx App.js
 <Button theme="primary" label="Select a photo" onPress={pickImageAsync} />

docs/pages/tutorial/eas/using-github.mdx

@@ -127,8 +127,8 @@ To automatically trigger a build using a GitHub PR label, we're going to utilize
 <ProgressTracker
   currentChapterIndex={10}
   name="EAS_TUTORIAL"
-  summary="In this chapter, we linked our GitHub account with Expo, connected our repository to our EAS project, and automated build creation using GitHub PR labels."
-  nextChapterDescription="Learn about the next steps in your journey to use EAS."
+  summary="We successfully linked our GitHub account with Expo, connected our repository to our EAS project, and learned about automated development build creation using GitHub PR labels."
+  nextChapterDescription="Learn about the next steps to use EAS."
   nextChapterTitle="Next steps in your journey with EAS"
   nextChapterLink="/tutorial/eas/next-steps/"
 />