Merge pull request #1933 from Youmoo/patch-1

Typo perhaps

content/fundamentals/dynamic-modules.md

@@ -117,7 +117,7 @@ In fact, what our `register()` method will return is a `DynamicModule`. A dynami
 
 ```typescript
 @Module({
-  imports: [DogsService],
+  imports: [DogsModule],
   controllers: [CatsController],
   providers: [CatsService],
   exports: [CatsService]
@@ -128,7 +128,7 @@ Dynamic modules must return an object with the exact same interface, plus one ad
 
 > info **Hint** For a dynamic module, all properties of the module options object are optional **except** `module`.
 
-What about the static `register()` method? We can now see that its job is to return an object that has the `DynamicModule` interface. When we call it, we are effectively providing a module to the `imports` list, similar to the way we would do so in the static case by listing a module class name. In other words, the dynamic module API simply returns a module, but rather than fix the properties in the `@Modules` decorator, we specify them programmatically.
+What about the static `register()` method? We can now see that its job is to return an object that has the `DynamicModule` interface. When we call it, we are effectively providing a module to the `imports` list, similar to the way we would do so in the static case by listing a module class name. In other words, the dynamic module API simply returns a module, but rather than fix the properties in the `@Module` decorator, we specify them programmatically.
 
 There are still a couple of details to cover to help make the picture complete: