edit pass: automation-child-runbooks

Author: ShawnJackson

articles/automation/automation-child-runbooks.md

@@ -24,7 +24,7 @@ There are two ways to call a child runbook: inline or through a cmdlet. The foll
 | **Automation Account** |The parent runbook can use only a child runbook in the same Automation account. |Parent runbooks can use a child runbook from any Automation account, from the same Azure subscription, and even from a different subscription to which you have a connection. |
 | **Publishing** |A child runbook must be published before the parent runbook is published. |A child runbook is published anytime before the parent runbook is started. |
 
-## Call a child runbook inline
+## Call a child runbook by using inline execution
 
 To call a runbook inline from another runbook, use the name of the runbook and provide values for its parameters, just like you would use an activity or a cmdlet. All runbooks in the same Automation account are available to all others to be used in this way. The parent runbook waits for the child runbook to finish before moving to the next line, and any output returns directly to the parent.
 

articles/automation/automation-runbook-output-and-messages.md

@@ -25,7 +25,7 @@ The following table briefly describes each stream with its behavior in the Azure
 
 ## Use the output stream
 
-The output stream is used for the output of objects created by a script or workflow when it runs correctly. Azure Automation primarily uses this stream for objects to be consumed by parent runbooks that call the [current runbook](automation-child-runbooks.md). When a parent [calls a runbook inline](automation-child-runbooks.md#invoke-a-child-runbook-using-inline-execution), the child returns data from the output stream to the parent.
+The output stream is used for the output of objects created by a script or workflow when it runs correctly. Azure Automation primarily uses this stream for objects to be consumed by parent runbooks that call the [current runbook](automation-child-runbooks.md). When a parent [calls a runbook inline](automation-child-runbooks.md#call-a-child-runbook-by-using-inline-execution), the child returns data from the output stream to the parent.
 
 Your runbook uses the output stream to communicate general information to the client only if it is never called by another runbook. As a best practice, however, you runbooks should typically use the [verbose stream](#write-output-to-verbose-stream) to communicate general information to the user.