Add a hint (#9767)

* Add a hint

* Update attributes.md

Author: imba-tjd

docs/csharp/tutorials/attributes.md

@@ -121,7 +121,7 @@ Attributes act as metadata. Without some outward force, they won't actually do a
 To find and act on attributes, [Reflection](../programming-guide/concepts/reflection.md) is generally needed. I won't cover Reflection in-depth in this tutorial, but the basic
 idea is that Reflection allows you to write code in C# that examines other code.
 
-For instance, you can use Reflection to get information about a class: 
+For instance, you can use Reflection to get information about a class(add `using System.Reflection;` at the head of your code): 
 
 [!code-csharp[Getting type information with Reflection](../../../samples/snippets/csharp/tutorials/attributes/Program.cs#ReflectionExample1)]
 

docs/framework/wcf/feature-details/troubleshooting-correlation.md

@@ -240,4 +240,4 @@ The following example shows a <xref:System.ServiceModel.Activities.Receive> acti
     <p1:OutArgument x:TypeArguments="m:AddItemMessage">[AddItemMessage]</p1:OutArgument>
   </ReceiveMessageContent>
 </Receive>
-```
+```

docs/standard/microservices-architecture/multi-container-microservice-net-applications/data-driven-crud-microservice.md

@@ -251,7 +251,7 @@ The docker-compose.yml files at the solution level are not only more flexible th
 
 Finally, you can get that value from your code by using Configuration\["ConnectionString"\], as shown in the ConfigureServices method in an earlier code example.
 
-However, for production environments, you might want to explore additional ways on how to store secrets like the connection strings. An excellent way to manage application secrets is using [Azure Key Vault}(https://azure.microsoft.com/services/key-vault/).
+However, for production environments, you might want to explore additional ways on how to store secrets like the connection strings. An excellent way to manage application secrets is using [Azure Key Vault](https://azure.microsoft.com/services/key-vault/).
 
 Azure Key Vault helps to store and safeguard cryptographic keys and secrets used by your cloud applications and services. A secret is anything you want to keep strict control of, like API keys, connection strings, passwords, etc. and strict control includes usage logging, setting expiration, managing access, <span class="underline">among others</span>.
 
@@ -427,4 +427,4 @@ It is that simple. And because it is automatically generated, the Swagger metada
 
 >[!div class="step-by-step"]
 >[Previous](microservice-application-design.md)
->[Next](multi-container-applications-docker-compose.md)
+>[Next](multi-container-applications-docker-compose.md)

docs/standard/modern-web-apps-azure-architecture/develop-asp-net-core-mvc-apps.md

@@ -77,7 +77,7 @@ ASP.NET Core has built-in support for and internally makes use of a technique kn
 
 Static cling occurs when your classes make calls to static methods, or access static properties, which have side effects or dependencies on infrastructure. For example, if you have a method that calls a static method, which in turn writes to a database, your method is tightly coupled to the database. Anything that breaks that database call will break your method. Testing such methods is notoriously difficult, since such tests either require commercial mocking libraries to mock the static calls, or can only be tested with a test database in place. Static calls that don't have any dependence on infrastructure, especially those that are completely stateless, are fine to call and have no impact on coupling or testability (beyond coupling code to the static call itself).
 
-Many developers understand the risks of static cling and global state, but will still tightly couple their code to specific implementations through direct instantiation. "New is glue" is meant to be a reminder of this coupling, and not a general condemnation of the use of the new keyword. Just as with static method calls, new instances of types that have no external dependencies typically do not tightly couple code to implementation details or make testing more difficult. But each time a class is instantiated, take just a brief moment to consider whether it makes sense to hard-code that specific instance in that particular location, or if it would be a better design to request that instance as a dependency.
+Many developers understand the risks of static cling and global state, but will still tightly couple their code to specific implementations through direct instantiation. "New is glue" is meant to be a reminder of this coupling, and not a general condemnation of the use of the `new` keyword. Just as with static method calls, new instances of types that have no external dependencies typically do not tightly couple code to implementation details or make testing more difficult. But each time a class is instantiated, take just a brief moment to consider whether it makes sense to hard-code that specific instance in that particular location, or if it would be a better design to request that instance as a dependency.
 
 ### Declare your dependencies