1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index f8cc3f8ed152..c64e969dc33b 100644
--- a/Documentation/HOWTO
+++ b/Documentation/HOWTO
@@ -208,7 +208,7 @@ tools.  One such tool that is particularly recommended is the Linux
 Cross-Reference project, which is able to present source code in a
 self-referential, indexed webpage format. An excellent up-to-date
 repository of the kernel code may be found at:
-        http://sosdg.org/~coywolf/lxr/
+        http://users.sosdg.org/~qiyong/lxr/
 The development process
@@ -384,7 +384,7 @@ One of the best ways to put into practice your hacking skills is by fixing
 bugs reported by other people. Not only you will help to make the kernel
 more stable, you'll learn to fix real world problems and you will improve
 your skills, and other developers will be aware of your presence. Fixing
-bugs is one of the best ways to earn merit amongst the developers, because
+bugs is one of the best ways to get merits among other developers, because
 not many people like wasting time fixing other people's bugs.
 To work in the already reported bug reports, go to http://bugzilla.kernel.org.

diff --git a/Documentation/HOWTO b/Documentation/HOWTO index f8cc3f8ed152..c64e969dc33b 100644 --- a/Documentation/HOWTO +++ b/Documentation/HOWTO
@@ -208,7 +208,7 @@ tools. One such tool that is particularly recommended is the Linux
208	Cross-Reference project, which is able to present source code in a	208	Cross-Reference project, which is able to present source code in a
209	self-referential, indexed webpage format. An excellent up-to-date	209	self-referential, indexed webpage format. An excellent up-to-date
210	repository of the kernel code may be found at:	210	repository of the kernel code may be found at:
211	http://sosdg.org/~coywolf/lxr/	211	http://users.sosdg.org/~qiyong/lxr/
212		212
213		213
214	The development process	214	The development process
@@ -384,7 +384,7 @@ One of the best ways to put into practice your hacking skills is by fixing
384	bugs reported by other people. Not only you will help to make the kernel	384	bugs reported by other people. Not only you will help to make the kernel
385	more stable, you'll learn to fix real world problems and you will improve	385	more stable, you'll learn to fix real world problems and you will improve
386	your skills, and other developers will be aware of your presence. Fixing	386	your skills, and other developers will be aware of your presence. Fixing
387	bugs is one of the best ways to earn merit amongst the developers, because	387	bugs is one of the best ways to get merits among other developers, because
388	not many people like wasting time fixing other people's bugs.	388	not many people like wasting time fixing other people's bugs.
389		389
390	To work in the already reported bug reports, go to http://bugzilla.kernel.org.	390	To work in the already reported bug reports, go to http://bugzilla.kernel.org.