updated naming article

Author: OlgaPodo

graph/articles/naming.md

@@ -1,12 +1,12 @@
-#  Naming guidelines
+#  Naming 
 ##  1. Approach
 Naming policies should aid developers in discovering functionality without having to constantly refer to documentation.
 Use of common patterns and standard conventions greatly aids developers in correctly guessing common property names and meanings.
-Services SHOULD use verbose naming patterns and SHOULD NOT use abbreviations other than acronyms that are the dominant mode of expression in the domain being represented by the API, (e.g. Url).
+Services SHOULD use verbose naming patterns and MUST NOT use abbreviations other than acronyms that are the dominant mode of expression in the domain being represented by the API, (e.g. Url).
 
 ##  2. Casing
 - Acronyms SHOULD follow the casing conventions as though they were regular words (e.g. Url).
-- All identifiers including namespaces, entityTypes, entitySets, properties, actions, functions and enumeration values SHOULD use lowerCamelCase.
+- All identifiers including namespaces, entityTypes, entitySets, properties, actions, functions and enumeration values MUST use lowerCamelCase.
 - HTTP headers are the exception and SHOULD use standard HTTP convention of Capitalized-Hyphenated-Terms.
 
 ##  3. Names to avoid

graph/articles/nullable.md

@@ -26,7 +26,7 @@ Below are some examples of nullable and non-nullable properties.
 
 ## HTTP Requests
 
-### {1} Create a servicePrincipal with no properties
+### 1. Create a servicePrincipal with no properties
 
 ```HTTP
 POST /servicePrincipals
@@ -40,7 +40,7 @@ POST /servicePrincipals
 }
 ```
 
-### {2} Create a servicePrincipal without a display name
+### 2. Create a servicePrincipal without a display name
 
 ```HTTP
 POST /servicePrincipals
@@ -62,7 +62,7 @@ Notes:
 2. `foo` has the default value as specified by its `DefaultValue` attribute in the CSDL
 3. `bar` has the default value as specified by its `DefaultValue` attribute in the CSDL
 
-### {3} Update the display name of a service principal to null
+### 3. Update the display name of a service principal to null
 
 ```HTTP
 PATCH /servicePrincipals/00000000-0000-0000-0000-000000000001
@@ -81,7 +81,7 @@ PATCH /servicePrincipals/00000000-0000-0000-0000-000000000001
 Notes:
 1. `displayName` cannot be set to `null` because it has be marked with `Nullable="false"` in the CSDL.
 
-### {4} Update the display name of a service principal
+### 4. Update the display name of a service principal
 
 ```HTTP
 PATCH /servicePrincipals/00000000-0000-0000-0000-000000000001
@@ -102,7 +102,7 @@ Notes:
 1. `displayName` can be set to any value other than `null`
 2. The response body here is provided for clarity, and is not part of the guidance itself. The [OData v4.01 standard](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateanEntity) states that the workload can decide the behavior.
 
-### {5} Update the foo property of a service principal to null
+### 5. Update the foo property of a service principal to null
 
 ```HTTP
 PATCH /servicePrincipals/00000000-0000-0000-0000-000000000001
@@ -123,7 +123,7 @@ Notes:
 1. `foo` can be set to `null` because it has be marked with `Nullable="true"` in the CSDL.
 2. The response body here is provided for clarity, and is not part of the guidance itself. The [OData v4.01 standard](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateanEntity) states that the workload can decide the behavior.
 
-### {6} Update the foo property of a service principal to a non-default value
+### 6. Update the foo property of a service principal to a non-default value
 
 ```HTTP
 PATCH /servicePrincipals/00000000-0000-0000-0000-000000000001
@@ -144,7 +144,7 @@ Notes:
 1. `foo` can be set to `something other than testval`
 2. The response body here is provided for clarity, and is not part of the guidance itself. The [OData v4.01 standard](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateanEntity) states that the workload can decide the behavior.
 
-### {7} Update the bar property of a service principal to null
+### 7. Update the bar property of a service principal to null
 
 ```HTTP
 PATCH /servicePrincipals/00000000-0000-0000-0000-000000000001
@@ -163,7 +163,7 @@ PATCH /servicePrincipals/00000000-0000-0000-0000-000000000001
 Notes:
 1. `bar` cannot be set to `null` because it has be marked with `Nullable="false"` in the CSDL.
 
-### {8} Update the bar property of a service principal to a non-default value
+### 8. Update the bar property of a service principal to a non-default value
 
 ```HTTP
 PATCH /servicePrincipals/00000000-0000-0000-0000-000000000001
@@ -184,7 +184,7 @@ Notes:
 1. `bar` can be set to `a new bar`
 2. The response body here is provided for clarity, and is not part of the guidance itself. The [OData v4.01 standard](https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateanEntity) states that the workload can decide the behavior.
 
-### {9} Create a service principal while customizing the display name
+### 9. Create a service principal while customizing the display name
 ```HTTP
 POST /servicePrincipals
 {
@@ -206,7 +206,7 @@ Notes:
 2. `foo` has the default value as specified by its `DefaultValue` attribute in the CSDL
 3. `bar` has the default value as specified by its `DefaultValue` attribute in the CSDL
 
-### {10} Create a service principal with a null display name
+### 10. Create a service principal with a null display name
 ```HTTP
 POST /servicePrincipals
 {
@@ -225,7 +225,7 @@ POST /servicePrincipals
 Notes:
 1. `displayName` isn't required to create a new `servicePrincipal`, but it *can* be provided; it *cannot* be provided as `null` because the property was marked with `Nullable="false"`
 
-### {11} Create a service principal with a value for the foo property
+### 11. Create a service principal with a value for the foo property
 ```HTTP
 POST /servicePrincipals
 {
@@ -247,7 +247,7 @@ Notes:
 2. `foo` isn't required to create a new `servicePrincipal`, but it *can* be provided; this is orthogonal to whether or not the property has `Nullable="true"` or `Nullable="false"`.
 3. `bar` has the default value as specified by its `DefaultValue` attribute in the CSDL
 
-### {12} Create a service principal with null for the foo property
+### 12. Create a service principal with null for the foo property
 ```HTTP
 POST /servicePrincipals
 {
@@ -269,7 +269,7 @@ Notes:
 2. `foo` isn't required to create a new `servicePrincipal`, but it *can* be provided; because the property has `Nullable="true"`, a `null` value can be provided for it.
 3. `bar` has the default value as specified by its `DefaultValue` attribute in the CSDL
 
-### {13} Create a service principal with a value for the bar property
+### 13. Create a service principal with a value for the bar property
 ```HTTP
 POST /servicePrincipals
 {
@@ -291,7 +291,7 @@ Notes:
 2. `foo` has the default value as specified by its `DefaultValue` attribute in the CSDL
 3. `bar` isn't required to create a new `servicePrincipal`, but it *can* be provided; this is orthogonal to whether or not the property has `Nullable="true"` or `Nullable="false"`.
 
-### {14} Create a service principal with null for the bar property
+### 14. Create a service principal with null for the bar property
 ```HTTP
 POST /servicePrincipals
 {

graph/patterns/long-running-operations.md

@@ -46,10 +46,6 @@ The RELO pattern is the preferred pattern for long running operations and should
 used wherever possible. The pattern avoids complexity, and consistent resource
 presentation makes things simpler for our users and tooling chain.
 
-In general, Microsoft Graph API guidelines for long running operations follow [Microsoft REST API
-Guidelines](https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md#13-long-running-operations).
-There are some deviations from the base guidelines where Microsoft Graph API standards require that you do one of the following:
-
 - For the RELO pattern, you should return the Location header that indicates the location of the resource.
   - The API response says the targeted resource is being created by returning a 201 status code and the resource URI is provided in the Location header, but the response indicates that the request is not completed by including "Provisioning" status.