Misc fixes (MicrosoftDocs#414)

matthiaswenz · conceptdev · commit 0fd6e9ad3835 · 2017-12-08T09:27:00.000-08:00
* Fix the order of items in the Android docs

* Fix GitHub spelling

* Fix Bitbucket spelling

* Replace some remnants of Mobile Center era
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,8 +1,8 @@
 # Contributing
 
-Thank you for your interest in contributing to the Mobile Center documentation!
+Thank you for your interest in contributing to the App Center documentation!
 
-In this topic, you'll see the basic process for adding or updating content in the [Mobile Center documentation site](https://docs.microsoft.com/mobile-center).
+In this topic, you'll see the basic process for adding or updating content in the [App Center documentation site](https://docs.microsoft.com/appcenter).
 
 In this topic, we'll cover:
 
@@ -52,7 +52,7 @@ The Visual Studio team will review your PR and let you know if the change looks
 
 The maintainers will merge your PR into the master branch once feedback has been applied and your change looks good.
 
-On a certain cadence, we push all commits from master branch into the live branch and then you'll be able to see your contribution live at https://docs.microsoft.com/mobile-center/.
+On a certain cadence, we push all commits from master branch into the live branch and then you'll be able to see your contribution live at https://docs.microsoft.com/appcenter/.
 
 ## DOs and DON'Ts
 
diff --git a/README.md b/README.md
@@ -1,12 +1,12 @@
-# Mobile Center Preview documentation
+# App Center documentation
 
-Welcome! This repo contains source files for the work-in-progress Mobile Center technical documentation. The topics are published on the [Mobile Center documentation site](https://docs.microsoft.com/mobile-center).
+Welcome! This repo contains source files for the work-in-progress App Center technical documentation. The topics are published on the [App Center documentation site](https://docs.microsoft.com/appcenter).
 
 ## Contributing to the documentation
 
 To contribute to this documentation, please see the [Contributing guide](CONTRIBUTING.md).
-We welcome your contributions to help us improve the Mobile Center docs. All the articles in this repository use GitHub flavored markdown.
+We welcome your contributions to help us improve the App Center docs. All the articles in this repository use GitHub flavored markdown.
 
-Several feature areas of Mobile Center have their own folders in this repo, such as **build** for topics on Build, **crashes** for topics on the Crash Reporting service, and so forth. The **/images** subfolder in each folder contains art files for the topics. The [Contributing guide](CONTRIBUTING.md) has more information.
+Several feature areas of App Center have their own folders in this repo, such as **build** for topics on Build, **crashes** for topics on the Crash Reporting service, and so forth. The **/images** subfolder in each folder contains art files for the topics. The [Contributing guide](CONTRIBUTING.md) has more information.
 
 This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
diff --git a/vs-mobile-center-docs/build/android/first-build.md b/vs-mobile-center-docs/build/android/first-build.md
@@ -38,19 +38,19 @@ By default, a new build is triggered every time a developer pushes to a configur
 ### 3.2. Build variant
 The available build variants will populate from the Build Types and Product Flavors specified in the build.gradle file. Select which build variant should be built.
 
-### 3.4. Increment version number
+### 3.3. Increment version number
 When enabled, the version code in the AndroidManifest.xml of your app automatically increments for each build. The change happens during the actual build and won't be committed to your repository.
 
-### 3.3. Code signing
+### 3.4. Code signing
 A successful build will produce an APK file. In order to release the build to the Play Store, it needs to be signed with a valid certificate stored in a keystore. To sign the builds produced from a branch, enable code signing in the configuration pane, upload your keystore to your repository, and provide the relevant credentials in the configuration pane. You can read more about code signing [here](~/build/android/code-signing.md).
 
-### 3.4. Launch your successful build on a real device
+### 3.5. Launch your successful build on a real device
 Use your newly produced APK file to test if your app starts on a real device. This will add approximately 10 more minutes to the total build time. Read more about it [here](~/build/build-test-integration.md)
 
-### 3.5. build.gradle File
+### 3.6. build.gradle File
 Specific information about your build will be collected from your Gradle file including dependencies, build tools version, build types, and product flavors.
 
-### 3.6. Distribute to a distribution group
+### 3.7. Distribute to a distribution group
 You can configure each successful build from a branch to be distributed to a previously created distribution group. You can add a new distribution group from within the Distribute section. There is always a default distribution group called "Collaborators" that includes all the users who have access to the app.
 
 Once you save the configuration, a new build will be kicked off automatically.
diff --git a/vs-mobile-center-docs/dashboard/bugtracker/index.md b/vs-mobile-center-docs/dashboard/bugtracker/index.md
@@ -1,6 +1,6 @@
 ---
 title: App Center bug tracker Documentation
-description: how to integrate App Center with bug trackers like Visual Studio Team Services (VSTS) and Github
+description: how to integrate App Center with bug trackers like Visual Studio Team Services (VSTS) and GitHub
 keywords: app center, appcenter, visual studio app center, visual studio appcenter, bug tracker, bugtracker, documentation, hockeyapp, VSTS, github
 author: amchew
 ms.author: amchew
@@ -13,7 +13,7 @@ ms.assetid: 97b6f745-736f-4abc-a85b-8834da2b51d4
 # App Center bug tracker integration
 ## Overview
 
-App Center has bug tracker integration for the crashes service. Users can be quickly informed about critical App Center events within the tools that you use regularly in your day to day flow for a seamless experience. App Center supports bug trackers like Visual Studio Team Services (VSTS) and Github. Users need to have manage or developer permissions to be able to create and configure the bug tracker.
+App Center has bug tracker integration for the crashes service. Users can be quickly informed about critical App Center events within the tools that you use regularly in your day to day flow for a seamless experience. App Center supports bug trackers like Visual Studio Team Services (VSTS) and GitHub. Users need to have manage or developer permissions to be able to create and configure the bug tracker.
 
 ## Getting Started
 
@@ -37,8 +37,8 @@ App Center has bug tracker integration for the crashes service. Users can be qui
 
 	1. For GitHub:
 
-		1. Login with your Github credentials and click **Authorize MobileCenter**.
-		1. Select which Github repository to integrate the bug tracker with and click **Next**.
+		1. Login with your GitHub credentials and click **Authorize MobileCenter**.
+		1. Select which GitHub repository to integrate the bug tracker with and click **Next**.
 		1. Under **Add Bug Tracker**, fill in fields for **Number of crashes** and click **Add**:
 			- Number of crashses is a threshold you can set for the minimum number of crashes to happen in a crash group before an issue is created in GitHub.
 
diff --git a/vs-mobile-center-docs/distribution/codepush/migrationguide.md b/vs-mobile-center-docs/distribution/codepush/migrationguide.md
@@ -158,7 +158,7 @@ appcenter codepush deployment list MyApp
 
 
 
-## Mobile Center CLI CodePush Cheat Sheet:
+## App Center CLI CodePush Cheat Sheet:
 
 | Command                               | Description                              |  Example               |
 | ------------------------------------- | ---------------------------------------- | ---------------------- |
diff --git a/vs-mobile-center-docs/general/changelog.md b/vs-mobile-center-docs/general/changelog.md
@@ -166,7 +166,7 @@ Create & manage your distribution groups, upload your release and distribute it
 
 ### **Mar 30, 2017**
 - Organizations: Share apps among your team members by creating and grouping them within an Organization. Find them under Settings.
-- Bitbucket: Connect to source code repositories using GitHub... and now BitBucket, too! VSTS support coming soon.  
+- Bitbucket: Connect to source code repositories using GitHub... and now Bitbucket, too! VSTS support coming soon.  
 - New Build commands in the CLI: Trigger a new build for pre-configured branches, view the build status of a branch, download logs for a build and get a list of branches for your app using CLI v0.7.0.
 - Build React Native apps with Yarn: Use the popular JavaScript package manager, Yarn, when building React Native apps. Dependency installs are now also faster and deterministic.
 - Release notes from your commits: When building, release notes now auto-populate with the corresponding commit message.  
diff --git a/vs-mobile-center-docs/quickstarts/android/getting-started.md b/vs-mobile-center-docs/quickstarts/android/getting-started.md
@@ -21,7 +21,7 @@ In this tutorial, you will learn how to set up a sample Android app with App Cen
 - Create [GitHub account](https://github.com/join).
 - [Download Android Studio](https://developer.android.com/studio/index.html) and [install it on your local machine](https://developer.android.com/studio/install.html).
 
-## Login to Github and fork the repository
+## Login to GitHub and fork the repository
 1. Login to your [GitHub account](https://github.com/join).
 2. Access the [sample app's GitHub repository](https://github.com/VSAppCenter/sampleapp-android).
 3. Click **Fork** at the top right hand corner of the page.
diff --git a/vs-mobile-center-docs/quickstarts/ios/getting-started.md b/vs-mobile-center-docs/quickstarts/ios/getting-started.md
@@ -30,7 +30,7 @@ In this tutorial, you will learn how to set up a sample Swift app with App Cente
 - [GitHub account](https://github.com/join)
 - [Xcode](https://itunes.apple.com/us/app/xcode/id497799835?mt=12#)
 
-## Login to Github and fork the repository
+## Login to GitHub and fork the repository
 1. Login to your [GitHub account](https://github.com/join).
 
 2. Access the [sample app's GitHub repository](https://github.com/VSAppCenter/sampleapp-ios-swift).
diff --git a/vs-mobile-center-docs/quickstarts/ios/push.md b/vs-mobile-center-docs/quickstarts/ios/push.md
@@ -41,7 +41,7 @@ First, follow the [getting started tutorial](getting-started.md) to set up the s
   If you encounter an error, your codesigning may not support Push Notifications. Go to the [Apple Developer portal](https://developer.apple.com/account/ios/identifier/bundle/) and edit the App ID to allow Push Notifications.
 
 ## Build and Distribute the app
-1. **Add, commit, and push the changes to Github.**
+1. **Add, commit, and push the changes to GitHub.**
 
 2. Follow the [Build tutorial](build.md) and then the [Distribute tutorial](distribute.md) to deploy the app **onto your device**. The push notification will not appear on a simulator.
 
diff --git a/vs-mobile-center-docs/quickstarts/macOS/getting-started.md b/vs-mobile-center-docs/quickstarts/macOS/getting-started.md
@@ -24,7 +24,7 @@ In this tutorial, you will learn how to set up a sample Swift app with App Cente
 - [GitHub account](https://github.com/join)
 - [Xcode](https://itunes.apple.com/us/app/xcode/id497799835?mt=12#)
 
-## Login to Github and fork the repository
+## Login to GitHub and fork the repository
 1. Login to your [GitHub account](https://github.com/join).
 
 2. Access the [sample app's GitHub repository](https://github.com/VSAppCenter/sampleapp-macos-swift).
diff --git a/vs-mobile-center-docs/quickstarts/macOS/push.md b/vs-mobile-center-docs/quickstarts/macOS/push.md
@@ -35,7 +35,7 @@ First, follow the [getting started tutorial](getting-started.md) to set up the s
   If you encounter an error, your codesigning may not support Push Notifications. Go to the [Apple Developer portal](https://developer.apple.com/account/mac/identifier/bundle/) and edit the App ID to allow Push Notifications.
 
 ## Build and Distribute the app
-1. **Add, commit, and push the changes to Github.**
+1. **Add, commit, and push the changes to GitHub.**
 
 2. Follow the [Build tutorial](build.md) and then the [Distribute tutorial](distribute.md) to deploy the app **onto your device**.
 
diff --git a/vs-mobile-center-docs/sdk/getting-started/react-native.md b/vs-mobile-center-docs/sdk/getting-started/react-native.md
@@ -150,7 +150,7 @@ We **strongly** recommend integrating the SDK via CocoaPods as described above.
 
 1. Download the [App Center SDK for React Native](https://github.com/Microsoft/appcenter-sdk-react-native/releases/latest) frameworks provided as a zip file.
 
-2. From the release notes on Github, please also download the corresponding frameworks of the App Center SDK for iOS.
+2. From the release notes on GitHub, please also download the corresponding frameworks of the App Center SDK for iOS.
 
 3. Unzip both archives and you will see a folder called **AppCenter-SDK-Apple/iOS** that contains different frameworks for each App Center service. The framework called `AppCenter` is required in the project as it contains code that is shared between the different modules. You will also see a folder named **AppCenterReactNativeShared** which contains a single framework for the React Native bridge for iOS which is also required.
 
diff --git a/vs-mobile-center-docs/test-cloud/preparing-for-upload/uitest.md b/vs-mobile-center-docs/test-cloud/preparing-for-upload/uitest.md
@@ -42,7 +42,7 @@ The command line parameters include the following pieces of information that is
 After the test run has been created, ensure that the following software is installed on the computer that will submit the tests: 
 
 1. Ensure that the computer has [Node.js](https://nodejs.org/en/) 6.3 installed.
-2. Install the [App Center CLI](~/cli/index.md). Instructions for [installing the App Center CLI](https://github.com/Microsoft/AppCenter-CLI#installation) maybe be found in the [README.md on Github](https://github.com/Microsoft/AppCenter-CLI).
+2. Install the [App Center CLI](~/cli/index.md). Instructions for [installing the App Center CLI](https://github.com/Microsoft/AppCenter-CLI#installation) maybe be found in the [README.md on GitHub](https://github.com/Microsoft/AppCenter-CLI).
 
 ## Preparing Xamarin.Android Apps
 
