typo: recieve -> receive

nschonni · nschonni · commit 1396dfd369bc · 2018-11-06T00:54:54.000-05:00
diff --git a/articles/active-directory/hybrid/reference-connect-sync-connector-version-history.md b/articles/active-directory/hybrid/reference-connect-sync-connector-version-history.md
@@ -105,7 +105,7 @@ Related links:
   * Web Service Connector Configuration Tool does not support usage of space symbols in JSON attribute names 
     * A Substitution pattern can be added manually to the WSConfigTool.exe.config file, e.g. ```<appSettings> <add key="JSONSpaceNamePattern" value="__" /> </appSettings>```
 > [!NOTE]
-> JSONSpaceNamePattern key is required as for export you will recieve the following error: Message: Empty name is not legal. 
+> JSONSpaceNamePattern key is required as for export you will receive the following error: Message: Empty name is not legal. 
 
 * Lotus Notes:
   * When the option **Allow custom certifiers for Organization/Organizational Units** is disabled then the connector fails during export (Update) After the export flow all attributes are exported to Domino but at the time of export a KeyNotFoundException is returned to Sync. 
diff --git a/articles/active-directory/saas-apps/kantegassoforbamboo-tutorial.md b/articles/active-directory/saas-apps/kantegassoforbamboo-tutorial.md
@@ -120,7 +120,7 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
 	In the **Sign-on URL** textbox, type a URL using the following pattern: `https://<server-base-url>/plugins/servlet/no.kantega.saml/sp/<uniqueid>/login`
 	 
 	> [!NOTE] 
-	> These values are not real. Update these values with the actual Identifier, Reply URL, and Sign-On URL. These values are recieved during the configuration of Bamboo plugin which is explained later in the tutorial.
+	> These values are not real. Update these values with the actual Identifier, Reply URL, and Sign-On URL. These values are received during the configuration of Bamboo plugin which is explained later in the tutorial.
 
 1. On the **SAML Signing Certificate** section, click **Metadata XML** and then save the metadata file on your computer.
 
diff --git a/articles/active-directory/saas-apps/kantegassoforbitbucket-tutorial.md b/articles/active-directory/saas-apps/kantegassoforbitbucket-tutorial.md
@@ -120,7 +120,7 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
 	In the **Sign-on URL** textbox, type a URL using the following pattern: `https://<server-base-url>/plugins/servlet/no.kantega.saml/sp/<uniqueid>/login`
 
 	> [!NOTE] 
-	> These values are not real. Update these values with the actual Identifier, Reply URL, and Sign-On URL. These values are recieved during the configuration of Bitbucket plugin which is explained later in the tutorial.
+	> These values are not real. Update these values with the actual Identifier, Reply URL, and Sign-On URL. These values are received during the configuration of Bitbucket plugin which is explained later in the tutorial.
 
 1. On the **SAML Signing Certificate** section, click **Metadata XML** and then save the metadata file on your computer.
 
diff --git a/articles/active-directory/saas-apps/kantegassoforfisheyecrucible-tutorial.md b/articles/active-directory/saas-apps/kantegassoforfisheyecrucible-tutorial.md
@@ -120,7 +120,7 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
     In the **Sign-on URL** textbox, type a URL using the following pattern: `https://<server-base-url>/plugins/servlet/no.kantega.saml/sp/<uniqueid>/login`
 	 
 	> [!NOTE] 
-	> These values are not real. Update these values with the actual Identifier, Reply URL, and Sign-On URL. These values are recieved during the configuration of FishEye/Crucible plugin which is explained later in the tutorial.
+	> These values are not real. Update these values with the actual Identifier, Reply URL, and Sign-On URL. These values are received during the configuration of FishEye/Crucible plugin which is explained later in the tutorial.
 
 1. On the **SAML Signing Certificate** section, click **Metadata XML** and then save the metadata file on your computer.
 
diff --git a/articles/active-directory/saas-apps/leapsome-tutorial.md b/articles/active-directory/saas-apps/leapsome-tutorial.md
@@ -173,7 +173,7 @@ In this section, you enable Azure AD single sign-on in the Azure portal and conf
 
 	b. Copy the **Login URL (point your users here to start login)** value and paste it into the **Sign-on URL** textbox in **Leapsome Domain and URLs** section on Azure portal.
 
-	c. Copy the **Reply URL (recieves response from your identity provider)** value and paste it into the **Reply URL** textbox in  **Leapsome Domain and URLs** section on Azure portal.
+	c. Copy the **Reply URL (receives response from your identity provider)** value and paste it into the **Reply URL** textbox in  **Leapsome Domain and URLs** section on Azure portal.
 
 	d. In the **SSO Login URL (provided by identity provider)** textbox, paste the value of **SAML Single Sign-On Service URL**, which you copied from the Azure portal.
 
diff --git a/articles/databox/data-box-portal-ui-admin.md b/articles/databox/data-box-portal-ui-admin.md
@@ -104,7 +104,7 @@ Perform the following steps to edit the order.
 
 ## Edit notification details
 
-You may need to change the users whom you want to recieve the order status emails. For instance, a user needs to be informed when the disk is delivered or picked up. Another user may need to be informed when the data copy is complete so he can verify the data is in the Azure storage account before deleting it from the source. In these instances, you can edit the notification details.
+You may need to change the users whom you want to receive the order status emails. For instance, a user needs to be informed when the disk is delivered or picked up. Another user may need to be informed when the data copy is complete so he can verify the data is in the Azure storage account before deleting it from the source. In these instances, you can edit the notification details.
 
 Perform the following steps to edit notification details.
 
@@ -124,7 +124,7 @@ Perform the following steps to edit notification details.
 |Processed     | Order processing is complete. <br> During order processing, following actions occur:<li>Disks are encrypted using AES-128 BitLocker encryption. </li> <li>The Data Box Disk are locked to prevent any unauthorized access.</li><li>The passkey that unlocks the disks is generated during this process.</li>        |
 |Dispatched     | Order has shipped. You should receive the order in 1-2 days.        |
 |Delivered     | Order was delivered to the address specified in the order.        |
-|Picked up     |Your return shipment was picked up. <br> Once the shipment is recieved at Azure datacenter, data will be automatically uploaded to Azure.         |
+|Picked up     |Your return shipment was picked up. <br> Once the shipment is received at Azure datacenter, data will be automatically uploaded to Azure.         |
 |Received     | Your disks were received at the Azure datacenter. Data copy will start soon.        |
 |Data copied     |Data copy is in progress.<br> Wait until the data copy is complete.         |
 |Completed       |Successfully completed the order.<br> Verfiy your data is in Azure before you delete the on-premises data from servers.         |
diff --git a/articles/iot-hub/iot-hub-java-java-file-upload.md b/articles/iot-hub/iot-hub-java-java-file-upload.md
@@ -171,7 +171,7 @@ You need the **iothubowner** connection string for your IoT Hub to complete this
       public void run() {
         try {
           while (true) {
-            System.out.println("Recieve file upload notifications...");
+            System.out.println("Receive file upload notifications...");
             FileUploadNotification fileUploadNotification = fileUploadNotificationReceiver.receive();
             if (fileUploadNotification != null) {
               System.out.println("File Upload notification received");
diff --git a/articles/iot-hub/iot-hub-python-python-c2d.md b/articles/iot-hub/iot-hub-python-python-c2d.md
@@ -112,7 +112,7 @@ In this section, you create a Python console app to simulate the device and rece
                 print ( iothub_client_error )
     ```
 
-1. Add the following code to initialize the client and wait to recieve the cloud-to-device message:
+1. Add the following code to initialize the client and wait to receive the cloud-to-device message:
    
     ```python
     def iothub_client_init():
@@ -284,9 +284,9 @@ You are now ready to run the applications.
    
     ![Run the app to send the cloud-to-device command][img-send-command]
    
-1. Note the message recieved by the device.
+1. Note the message received by the device.
 
-    ![Message received][img-message-recieved]
+    ![Message received][img-message-received]
 
 
 ## Next steps
@@ -299,7 +299,7 @@ To learn more about developing solutions with IoT Hub, see the [IoT Hub develope
 <!-- Images -->
 [img-simulated-device]: media/iot-hub-python-python-c2d/simulated-device.png
 [img-send-command]:  media/iot-hub-python-python-c2d/send-command.png
-[img-message-recieved]: media/iot-hub-python-python-c2d/message-recieved.png
+[img-message-received]: media/iot-hub-python-python-c2d/message-received.png
 
 <!-- Links -->
 [lnk-python-download]: https://www.python.org/downloads/
diff --git a/articles/iot-hub/media/iot-hub-python-python-c2d/message-received.png b/articles/iot-hub/media/iot-hub-python-python-c2d/message-received.png
diff --git a/articles/log-analytics/log-analytics-agent-linux-support.md b/articles/log-analytics/log-analytics-agent-linux-support.md
@@ -212,7 +212,7 @@ This is a known issue that occurs on first upload of Linux data into a Log Analy
 
 ### Resolution
 * Verify the configuration in the Log Analytics workspace for Syslog has all the facilities and the correct log levels. Review [configure Syslog collection in the Azure portal](log-analytics-data-sources-syslog.md#configure-syslog-in-the-azure-portal)
-* Verify the native syslog messaging daemons (`rsyslog`, `syslog-ng`) are able to recieve the forwarded messages
+* Verify the native syslog messaging daemons (`rsyslog`, `syslog-ng`) are able to receive the forwarded messages
 * Check firewall settings on the Syslog server to ensure that messages are not being blocked
 * Simulate a Syslog message to Log Analytics using `logger` command
   * `logger -p local0.err "This is my test message"`
diff --git a/articles/machine-learning/service/how-to-configure-auto-train.md b/articles/machine-learning/service/how-to-configure-auto-train.md
@@ -187,7 +187,7 @@ Property |	Description	| Default Value
 `max_time_sec` |	Limits the amount of time (seconds) a particular iteration takes. If an iteration exceeds the specified amount, that iteration gets canceled. If not set, then the iteration continues to run until it is finished. |	None
 `n_cross_validations`	|Number of cross validation splits|	None
 `validation_size`	|Size of validation set as percentage of all training sample.|	None
-`preprocess` | True/False <br/>True enables experiment to perform preprocessing on the input. Following is a subset of preprocessing<li>Missing Data: Imputes the missing data- Numberical with Average, Text with most occurrence </li><li>Categorical Values: If data type is numeric and number of unique values is less than 5 percent, Converts into one-hot encoding </li><li>Etc. for complete list check [the GitHub repository](https://aka.ms/aml-notebooks)</li><br/>Note : if data is sparse you cannot use preprocess = true |	False |	
+`preprocess` | True/False <br/>True enables experiment to perform preprocessing on the input. Following is a subset of preprocessing<li>Missing Data: Imputes the missing data- Numerical with Average, Text with most occurrence </li><li>Categorical Values: If data type is numeric and number of unique values is less than 5 percent, Converts into one-hot encoding </li><li>Etc. for complete list check [the GitHub repository](https://aka.ms/aml-notebooks)</li><br/>Note : if data is sparse you cannot use preprocess = true |	False |	
 `blacklist_algos`	| Automated ML experiment has many different algorithms that it tries. Configure Automated ML to exclude certain algorithms from the experiment. Useful if you are aware that algorithm(s) do not work well for your dataset. Excluding algorithms can save you compute resources and training time.<br/>Allowed values for Classification<br/><li>logistic regression</li><li>SGD classifier</li><li>MultinomialNB</li><li>BernoulliNB</li><li>SVM</li><li>LinearSVM</li><li>kNN</li><li>DT</li><li>RF</li><li>extra trees</li><li>gradient boosting</li><li>lgbm_classifier</li><br/>Allowed values for Regression<br/><li>Elastic net</li><li>Gradient boosting regressor</li><li>DT regressor</li><li>kNN regressor</li><li>Lasso lars</li><li>SGD regressor</li><li>RF regressor</li><li>extra trees regressor</li>|	None
 `verbosity`	|Controls the level of logging with INFO being the most verbose and CRITICAL being the least.<br/>Allowed values are:<br/><li>logging.INFO</li><li>logging.WARNING</li><li>logging.ERROR</li><li>logging.CRITICAL</li>	| logging.INFO</li> 
 `X`	| All features to train with |	None
diff --git a/articles/monitoring-and-diagnostics/monitoring-supported-metrics.md b/articles/monitoring-and-diagnostics/monitoring-supported-metrics.md
@@ -813,7 +813,7 @@ Azure Monitor provides several ways to interact with metrics, including charting
 |IsEngineAnsweringQuery|Keep Alive|Count|Average|Sanity check indicates the cluster respondes to queries|No Dimensions|
 |IngestCommandOriginalSizeInMb|Ingestion Volume (In MB)|Count|Total|Overall volume of ingested data to the cluster (in MB)|No Dimensions|
 |EventAgeSeconds|Ingestion Latency (In seconds)|Seconds|Average|Ingestion time from the source (e.g. message is in EventHub) to the cluster in seconds|No Dimensions|
-|EventRecievedFromEventHub|Events Processed (for Event Hubs)|Count|Total|Number of events processed by the cluster when ingesting from Event Hub|No Dimensions|
+|EventReceivedFromEventHub|Events Processed (for Event Hubs)|Count|Total|Number of events processed by the cluster when ingesting from Event Hub|No Dimensions|
 |IngestionResult|Ingestion Result|Count|Count|Number of ingestion operations|IngestionResultDetails|
 |EngineCPU|CPU|Percent|Average|CPU utilization level|No Dimensions|
 
diff --git a/articles/partner-twilio-ruby-how-to-use-voice-sms.md b/articles/partner-twilio-ruby-how-to-use-voice-sms.md
@@ -142,7 +142,7 @@ If you open-up `http://yourdomain.cloudapp.net/make_call` in a browser, that wil
 
 The third parameter (`url`) is the URL that Twilio requests to get instructions on what to do once the call is connected. In this case we set-up a URL (`http://yourdomain.cloudapp.net`) that returns a simple TwiML document and uses the `<Say>` verb to do some text-to-speech and say "Hello Monkey" to the person recieving the call.
 
-## <a id="howto_recieve_sms"></a>How to: Recieve an SMS message
+## <a id="howto_receive_sms"></a>How to: Receive an SMS message
 In the previous example we initiated an **outgoing** phone call. This time, let's use the phone number that Twilio gave us during sign-up to process an **incoming** SMS message.
 
 First, log-in to your [Twilio dashboard][twilio_account]. Click on "Numbers" in the top nav and then click on the Twilio number you were provided. You'll see two URLs that you can configure. A Voice Request URL and an SMS Request URL. These are the URLs that Twilio calls whenever a phone call is made or an SMS is sent to your number. The URLs are also known as "web hooks".
diff --git a/articles/service-bus-messaging/service-bus-amqp-protocol-guide.md b/articles/service-bus-messaging/service-bus-amqp-protocol-guide.md
@@ -254,7 +254,7 @@ The operations are grouped by an identifier `txn-id`.
 
 For transactional interaction, the client acts as a `transaction controller` , which controls the operations that should be grouped together. Service Bus Service acts as a `transactional resource` and performs work as requested by the `transaction controller`.
 
-The client and service communicate over a `control link` , which is established by the client. The `declare` and `discharge` messages are sent by the controller over the control link to allocate and complete transactions respectively (they do not represent the demarcation of transactional work). The actual send/recieve is not performed on this link. Each transactional operation requested is explicitly identified with the desired `txn-id` and therefore may occur on any link on the Connection. If the control link is closed while there exist non-discharged transactions it created, then all such transactions are immediately rolled back, and attempts to perform further transactional work on them will lead to failure. Messages on control link must not be pre settled.
+The client and service communicate over a `control link` , which is established by the client. The `declare` and `discharge` messages are sent by the controller over the control link to allocate and complete transactions respectively (they do not represent the demarcation of transactional work). The actual send/receive is not performed on this link. Each transactional operation requested is explicitly identified with the desired `txn-id` and therefore may occur on any link on the Connection. If the control link is closed while there exist non-discharged transactions it created, then all such transactions are immediately rolled back, and attempts to perform further transactional work on them will lead to failure. Messages on control link must not be pre settled.
 
 Every connection has to initiate its own control link to be able to start and end transactions. The service defines a special target that functions as a `coordinator`. The client/controller establishes a control link to this target. Control link is outside the boundary of an entity, that is, same control link can be used to initiate and discharge transactions for multiple entities.
 
diff --git a/articles/storage/common/storage-import-export-data-from-blobs.md b/articles/storage/common/storage-import-export-data-from-blobs.md
@@ -82,7 +82,7 @@ Perform the following steps to create an export job in the Azure portal.
     - Provide a complete and valid contact name, phone, email, street address, city, zip, state/province and country/region.
 
         > [!TIP] 
-        > Instead of specifying an email address for a single user, provide a group email. This ensures that you recieve notifications even if an admin leaves.
+        > Instead of specifying an email address for a single user, provide a group email. This ensures that you receive notifications even if an admin leaves.
    
 5. In **Summary**:
 
diff --git a/articles/storage/common/storage-import-export-data-to-blobs.md b/articles/storage/common/storage-import-export-data-to-blobs.md
@@ -113,7 +113,7 @@ Perform the following steps to create an import job in the Azure portal.
     - Provide a complete and valid contact name, phone, email, street address, city, zip, state/province and country/region. 
         
         > [!TIP] 
-        > Instead of specifying an email address for a single user, provide a group email. This ensures that you recieve notifications even if an admin leaves.
+        > Instead of specifying an email address for a single user, provide a group email. This ensures that you receive notifications even if an admin leaves.
 
     ![Create import job - Step 3](./media/storage-import-export-data-to-blobs/import-to-blob5.png)
    
diff --git a/articles/storage/common/storage-import-export-data-to-files.md b/articles/storage/common/storage-import-export-data-to-files.md
@@ -144,7 +144,7 @@ Perform the following steps to create an import job in the Azure portal.
     - Provide a complete and valid contact name, phone, email, street address, city, zip, state/province and country/region.
 
         > [!TIP] 
-        > Instead of specifying an email address for a single user, provide a group email. This ensures that you recieve notifications even if an admin leaves.
+        > Instead of specifying an email address for a single user, provide a group email. This ensures that you receive notifications even if an admin leaves.
 
        ![Create import job - Step 3](./media/storage-import-export-data-to-blobs/import-to-blob5.png)
 
diff --git a/articles/store-sendgrid-php-how-to-send-email.md b/articles/store-sendgrid-php-how-to-send-email.md
@@ -183,7 +183,7 @@ code to the example script for sending an email with Swift Mailer.
   * Create the body of the message (a plain-text and an HTML version).
   * $text is your plain-text email
   * $html is your html version of the email
-  * If the reciever is able to view html emails then only the html
+  * If the receiver is able to view html emails then only the html
   * email will be displayed
   */
  $text = "Hi!\nHow are you?\n";
