Fixed Git issues

Author: spelluru

articles/azure-relay/includes/relay-hybrid-connections-http-requests-dotnet-get-started-client.md

@@ -43,9 +43,16 @@ In Visual Studio, create a new **Console App (.NET Framework)** project.
 2. Add constants to the `Program` class for the hybrid connection details. Replace the placeholders in brackets with the values that you obtained when you created the hybrid connection. Be sure to use the fully qualified namespace name.
 
     ```csharp
+    // replace {RelayNamespace} with the name of your namespace
     private const string RelayNamespace = "{RelayNamespace}.servicebus.windows.net";
+
+    // replace {HybridConnectionName} with the name of your hybrid connection
     private const string ConnectionName = "{HybridConnectionName}";
+
+    // replace {SAKKeyName} with the name of your Shared Access Policies key, which is RootManageSharedAccessKey by default
     private const string KeyName = "{SASKeyName}";
+
+    // replace {SASKey} with the primary key of the namespace you saved earlier
     private const string Key = "{SASKey}";
     ```
 3. Add the following method to the `Program` class:

articles/azure-relay/includes/relay-hybrid-connections-http-requests-java-get-started-client.md

@@ -79,10 +79,10 @@ of the `azure-relay` mvn package. This package provides functions to construct R
     }
     ```
     Replace the placeholders in brackets with the values you obtained when you created the hybrid connection.
-    1. `namespace` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
-    2. `path` - The name of the hybrid connection.
-    3. `keyrule` - The name of the SAS key.
-    4. `key` - The SAS key value.
+    - `namespace` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
+    - `path` - The name of the hybrid connection.
+    - `keyrule` - Name of your Shared Access Policies key, which is `RootManageSharedAccessKey` by default.
+    - `nst key` -   The primary key of the namespace you saved earlier.
 
 5. Add the following code to the `Sender.java` file, below is the expected main function for your java class: 
 

articles/azure-relay/includes/relay-hybrid-connections-http-requests-java-get-started-server.md

@@ -77,10 +77,10 @@ Run `mvn dependency:copy-dependencies -DoutputDirectory=lib` in your mvn project
 
     Replace the placeholders in brackets with the values you obtained when you created the hybrid connection.
 
-    1. `namespace` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
-    2. `path` - The name of the hybrid connection.
-    3. `keyrule` - The name of the SAS key.
-    4. `key` - The SAS key value.
+    - `namespace` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
+    - `path` - The name of the hybrid connection.
+    - `keyrule` - Name of your Shared Access Policies key, which is `RootManageSharedAccessKey` by default.
+    - `nst key` -   The primary key of the namespace you saved earlier.
 
 4. Add the following code to the `Listener.java` file, below is the expected main function for your java class: 
 

articles/azure-relay/includes/relay-hybrid-connections-http-requests-node-get-started-client.md

@@ -36,10 +36,10 @@ the package provides functions to construct Relay URIs and tokens.
 
 2. Add the following constants to the `sender.js` file for the hybrid connection details. Replace the placeholders in brackets with the values you obtained when you created the hybrid connection.
 
-   1. `const ns` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
-   2. `const path` - The name of the hybrid connection.
-   3. `const keyrule` - The name of the SAS key.
-   4. `const key` - The SAS key value.
+   - `const ns` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
+   - `const path` - The name of the hybrid connection.
+   - `const keyrule` - Name of your Shared Access Policies key, which is `RootManageSharedAccessKey` by default.
+   - `const key` -   The primary key of the namespace you saved earlier.
 
 3. Add the following code to the `sender.js` file. You will notice that the
    code does not differ significantly from the regular use of the Node.js

articles/azure-relay/includes/relay-hybrid-connections-http-requests-node-get-started-server.md

@@ -30,10 +30,10 @@ Run `npm install hyco-https` from a Node command prompt in your project folder.
    connection details. Replace the placeholders in brackets with the values you
    obtained when you created the hybrid connection.
 
-   1. `const ns` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
-   2. `const path` - The name of the hybrid connection.
-   3. `const keyrule` - The name of the SAS key.
-   4. `const key` - The SAS key value.
+   - `const ns` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
+   - `const path` - The name of the hybrid connection.
+   - `const keyrule` - Name of your Shared Access Policies key, which is `RootManageSharedAccessKey` by default.
+   - `const key` -   The primary key of the namespace you saved earlier.
 
 3. Add the following code to the `listener.js` file. :
 

articles/azure-relay/includes/relay-hybrid-connections-node-get-started-client.md

@@ -27,10 +27,10 @@ Run `npm install hyco-ws` from a Node command prompt in your project folder.
     ```
 2. Add the following constants to the `sender.js` file for the hybrid connection details. Replace the placeholders in brackets with the values you obtained when you created the hybrid connection.
 
-   1. `const ns` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
-   2. `const path` - The name of the hybrid connection.
-   3. `const keyrule` - The name of the SAS key.
-   4. `const key` - The SAS key value.
+   - `const ns` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
+   - `const path` - The name of the hybrid connection.
+   - `const keyrule` - Name of your Shared Access Policies key, which is `RootManageSharedAccessKey` by default.
+   - `const key` -   The primary key of the namespace you saved earlier.
 
 3. Add the following code to the `sender.js` file:
 

articles/azure-relay/includes/relay-hybrid-connections-node-get-started-server.md

@@ -22,10 +22,10 @@ Run `npm install hyco-ws` from a Node command prompt in your project folder.
     ```
 2. Add the following constants to the `listener.js` file for the hybrid connection details. Replace the placeholders in brackets with the values you obtained when you created the hybrid connection.
 
-   1. `const ns` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
-   2. `const path` - The name of the hybrid connection.
-   3. `const keyrule` - The name of the SAS key.
-   4. `const key` - The SAS key value.
+   - `const ns` - The Relay namespace. Be sure to use the fully qualified namespace name; for example, `{namespace}.servicebus.windows.net`.
+   - `const path` - The name of the hybrid connection.
+   - `const keyrule` - Name of your Shared Access Policies key, which is `RootManageSharedAccessKey` by default.
+   - `const key` -   The primary key of the namespace you saved earlier.
 
 3. Add the following code to the `listener.js` file:
 

articles/service-bus-messaging/service-bus-partitioning.md

@@ -112,8 +112,9 @@ Service Bus supports automatic message forwarding from, to, or between partition
 ## Partitioned entities limitations
 Currently Service Bus imposes the following limitations on partitioned queues and topics:
 
-* Partitioned queues and topics don't support sending messages that belong to different sessions in a single transaction.
-* Service Bus currently allows up to 100 partitioned queues or topics per namespace for the Basic and Standard SKU. Each partitioned queue or topic counts towards the quota of 10,000 entities per namespace.
+- For partitioned premium namespaces, the message size is limited to 1 MB when the messages are sent individually, and the batch size is limited to 1 MB when the messages are sent in a batch.
+- Partitioned queues and topics don't support sending messages that belong to different sessions in a single transaction.
+- Service Bus currently allows up to 100 partitioned queues or topics per namespace for the Basic and Standard SKU. Each partitioned queue or topic counts towards the quota of 10,000 entities per namespace.
 
 ## Next steps
 You can enable partitioning by using Azure portal, PowerShell, CLI, Resource Manager template, .NET, Java, Python, and JavaScript. For more information, see [Enable partitioning (Basic / Standard)](enable-partitions-basic-standard.md).