try again

Author: pragnagopa

articles/azure-functions/functions-reference-java.md

@@ -21,7 +21,7 @@ ms.author: routlaw
 
 The concepts of [triggers and bindings](functions-triggers-bindings.md) are fundamental to Azure Functions. Triggers start the execution of your code. Bindings give you a way to pass data to and return data from a function, without having to write custom data access code.
 
-A function should be a stateless method to process input and produce output. Your function cannot depend on any instance fields of the class. All the function methods should be `public` and method with annotation @FunctionName must be unique as method name defines the entry for a function.
+A function should be a stateless method to process input and produce output. Your function should not depend on any instance fields of the class. All the function methods should be `public` and method with annotation @FunctionName must be unique as method name defines the entry for a function.
 
 ## Folder structure
 
@@ -57,7 +57,7 @@ You can put more than one function in a project. Avoid putting your functions in
 
  Azure functions are invoked by a trigger, such as an HTTP request, a timer, or an update to data. Your function needs to process that trigger and any other inputs to produce one or more outputs.
 
-Use the Java annotations included in the [com.microsoft.azure.functions.annotation.*](/java/api/com.microsoft.azure.functions.annotation) package to bind input and outputs to your methods. See [Java reference docs](/java/api/com.microsoft.azure.functions.annotation) for more details.
+Use the Java annotations included in the [com.microsoft.azure.functions.annotation.*](/java/api/com.microsoft.azure.functions.annotation) package to bind input and outputs to your methods. For more information see [Java reference docs](/java/api/com.microsoft.azure.functions.annotation).
 
 > [!IMPORTANT] 
 > You must configure an Azure Storage account in your [local.settings.json](/azure/azure-functions/functions-run-local#local-settings-file) to run Azure Storage Blob, Queue, or Table triggers locally.
@@ -114,7 +114,7 @@ You can use Plain old Java objects (POJOs), types defined in `azure-functions-ja
 
 ### Plain old Java objects (POJOs)
 
-For converting input data to POJO, [azure-functions-java-worker](https://github.com/Azure/azure-functions-java-worker) uses [gson](https://github.com/google/gson) library. POJO types used as inputs to functions must the same `public` access modifier as the function methods they are being used in. 
+For converting input data to POJO, [azure-functions-java-worker](https://github.com/Azure/azure-functions-java-worker) uses [gson](https://github.com/google/gson) library. POJO types used as inputs to functions should be `public`.
 
 ### Binary data
 
@@ -174,9 +174,11 @@ public class Function {
 }
 ```
 
-This function is invoked with an HTTP request. HTTP request payload is passed as a `String` for the argument `inputReq`; and one entry is retrieved from the Azure Table Storage and is passed as `TestInputData` to the argument `inputData`.
+This function is invoked with an HTTP request. 
+- HTTP request payload is passed as a `String` for the argument `inputReq`
+- One entry is retrieved from the Azure Table Storage and is passed as `TestInputData` to the argument `inputData`.
 
-To receive a batch of inputs bind to `String[]`, `POJO[]`, `List<String>` or `List<POJO>`
+To receive a batch of inputs, you can bind to `String[]`, `POJO[]`, `List<String>` or `List<POJO>`.
 
 ```java
 @FunctionName("ProcessIotMessages")
@@ -329,7 +331,7 @@ public class Function {
 
 ## View logs and trace
 
-You can use the Azure CLI to stream Java standard out and error logging as well as other application logging. 
+You can use the Azure CLI to stream Java stdout and stderr logging as well as other application logging. 
 
 Configure your Function application to write application logging using the Azure CLI: