fix sentence

Author: juliakm

docs/pipelines/process/conditions.md

@@ -290,7 +290,7 @@ When you declare a parameter in the same pipeline that you have a condition, par
 
 The `condition` in the pipeline combines two functions: `succeeded()` and `eq('${{ parameters.doThing }}', true)`. The `succeeded()` function checks if the previous step succeeded. The `succeeded()` function returns true because there was no previous step. 
 
-The `eq('${{ parameters.doThing }}', true)` function checks whether the doThing parameter is equal to `true`. Since the default value for doThing is true, the condition will return true by default unless a different values gets set in the pipeline. 
+The `eq('${{ parameters.doThing }}', true)` function checks whether the doThing parameter is equal to `true`. Since the default value for doThing is true, the condition will return true by default unless a different value gets set in the pipeline. 
 
 For more template parameter examples, see [Template types & usage](templates.md). 
 

docs/pipelines/process/environments.md

@@ -181,7 +181,7 @@ A: These are some of the possible reasons of the failure:
 
   * In the following flows, Azure Pipelines doesn't have information about the user creating the environment: you update the YAML file using another external code editor, add a reference to an environment  that doesn't exist, and then cause a manual or continuous integration pipeline to be triggered. In this case, Azure Pipelines doesn't know about the user. Previously, we handled this case by adding all the project contributors to the administrator role of the environment. Any member of the project could then change these permissions and prevent others from accessing the environment. 
 
-  * You can use [variables](./variables.md?tabs=yaml%2cbatch&view=azure-devops&preserve-view=true) to create the environment or use the [Use templateContext to pass properties to templates](template-parameters.md#use-templatecontext-to-pass-properties-to-templates)templateContext property to pass values to stages, steps, and jobs that are used as parameters in a template. [Runtime parameters](runtime-parameters.md) won't work when creating the environment because they are expanded at run time. 
+  * You can use [variables](./variables.md?tabs=yaml%2cbatch&view=azure-devops&preserve-view=true) to create the environment or use [templateContext to pass properties to templates](template-parameters.md#use-templatecontext-to-pass-properties-to-templates). [Runtime parameters](runtime-parameters.md) won't work when creating the environment because they are expanded at run time. 
 
   * A user with stakeholder access level can't create the environment as stakeholders don't have access to the repository.
 

docs/pipelines/process/template-expressions.md

@@ -336,6 +336,3 @@ To help prevent runaway growth, Azure Pipelines imposes the following limits:
 - No more than 100 separate YAML files may be included (directly or indirectly)
 - No more than 20 levels of template nesting (templates including other templates)
 - No more than 10 megabytes of memory consumed while parsing the YAML (in practice, this is typically between 600 KB - 2 MB of on-disk YAML, depending on the specific features used)
-
-::: moniker-end
-