From d750b1e10d297630392193cc7705870b5a2dc149 Mon Sep 17 00:00:00 2001
From: alimemonzx <alimemonsd@gmail.com>
Date: Sat, 13 Apr 2019 21:28:36 +0100
Subject: [PATCH] docs: fix filename in example headers for provider guides
 (#29889)

PR Close #29889
---
 aio/content/guide/providers.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/aio/content/guide/providers.md b/aio/content/guide/providers.md
index 3024a71c1a..879e53ba8a 100644
--- a/aio/content/guide/providers.md
+++ b/aio/content/guide/providers.md
@@ -21,7 +21,7 @@ ng generate service User
 
 This command creates the following `UserService` skeleton:
 
-<code-example path="providers/src/app/user.service.0.ts"  header="src/app/user.service.0.ts" linenums="false"> </code-example>
+<code-example path="providers/src/app/user.service.0.ts"  header="src/app/user.service.ts" linenums="false"> </code-example>
 
 You can now inject `UserService` anywhere in your application.
 
@@ -38,7 +38,7 @@ You should always provide your service in the root injector unless there is a ca
 
 It's also possible to specify that a service should be provided in a particular `@NgModule`. For example, if you don't want `UserService` to be available to applications unless they import a `UserModule` you've created, you can specify that the service should be provided in the module:
 
-<code-example path="providers/src/app/user.service.1.ts"  header="src/app/user.service.1.ts" linenums="false">  </code-example>
+<code-example path="providers/src/app/user.service.1.ts"  header="src/app/user.service.ts" linenums="false">  </code-example>
 
 The example above shows the preferred way to provide a service in a module. This method is preferred because it enables tree-shaking of the service if nothing injects it. If it's not possible to specify in the service which module should provide it, you can also declare a provider for the service within the module: