Update components.md

Author: Mick Lawitzke

content/components.md

@@ -206,14 +206,9 @@ This is how our directory structure should look now:
 
 #### Manual instantiation
 
-Thus far, we've discussed how Nest automatically handles most of the details of resolving dependencies.  In certain circumstances, you may need to step outside of the built-in Dependency Injection system and manually retrieve or instantiate providers.  We briefly discuss two such topics below.
+Thus far, we've discussed how Nest automatically handles most of the details of resolving dependencies.  In certain circumstances, you may need to step outside of the built-in Dependency Injection system and manually retrieve or instantiate providers. We briefly discuss two such topics below.
 
  To get existing instances, or instantiate providers dynamically, you can use [Module reference](https://docs.nestjs.com/fundamentals/module-ref).
 
  To get providers within the `bootstrap()` function (for example for standalone applications without controllers, or to utilize a configuration service during bootstrapping) see [Standalone applications](https://docs.nestjs.com/standalone-applications).
 To get existing or instantiate providers dynamically you can use [Module reference](https://docs.nestjs.com/fundamentals/module-ref).
-
-#### Get providers inside bootstrap()
-To get providers within the `bootsrap()` function, e.g. for standalone applications without controllers, see [Standalone applications](https://docs.nestjs.com/standalone-applications)
-
-#### Get / Instantiate providers dynamically