diff --git a/docs/site/Booting-an-Application.md b/docs/site/Booting-an-Application.md
index b7120668020d..9340171a0f9f 100644
--- a/docs/site/Booting-an-Application.md
+++ b/docs/site/Booting-an-Application.md
@@ -185,7 +185,7 @@ a part of the `@loopback/boot` package and loaded automatically via `BootMixin`.
 
 ### Controller Booter
 
-This Booter's purpose is to discover [Controller](Controllers.html) type Artifacts and to bind
+This Booter's purpose is to discover [Controller](Controllers.md) type Artifacts and to bind
 them to the Application's Context.
 
 You can configure the conventions used in your
@@ -201,7 +201,7 @@ of your Application. The `controllers` object supports the following options:
 
 ### Repository Booter
 
-This Booter's purpose is to discover [Repository](Repository.html) type Artifacts and to bind
+This Booter's purpose is to discover [Repository](Repositories.md) type Artifacts and to bind
 them to the Application's Context. The use of this Booter requires `RepositoryMixin`
 from `@loopback/repository` to be mixed into your Application class.
 
diff --git a/docs/site/Implementing-features.md b/docs/site/Implementing-features.md
index 350336da23d7..c84a482a4aea 100644
--- a/docs/site/Implementing-features.md
+++ b/docs/site/Implementing-features.md
@@ -9,7 +9,7 @@ summary:
 ---
 
 {% include previous.html content="
-This article continues off from [Defining your testing stategy(./Defining-your-testing-strategy.md).
+This article continues from [Defining your testing stategy(./Defining-your-testing-strategy.md).
 " %}
 
 ## Incrementally implement features
diff --git a/docs/site/Testing-your-application.md b/docs/site/Testing-your-application.md
index e93f179d48eb..9e486adf9c6f 100644
--- a/docs/site/Testing-your-application.md
+++ b/docs/site/Testing-your-application.md
@@ -28,8 +28,8 @@ or [`given/when/then`](https://martinfowler.com/bliki/GivenWhenThen.html).
 Both styles work well, so pick one that you're comfortable with and
 start writing tests!
 
-For an introduction to automated testing, see [Define your testing strategy](Defining-your-testing-strategy.html).
-For a step-by-step tutorial, see [Incrementally implement features](Implementing-features.html).
+For an introduction to automated testing, see [Define your testing strategy](Defining-your-testing-strategy.md).
+For a step-by-step tutorial, see [Incrementally implement features](Implementing-features.md).
 
 {% include important.html content="
 A great test suite requires you to think smaller and favor fast and focused
@@ -318,9 +318,9 @@ produces code that's difficult to comprehend.
 #### Create a stub Repository
 
 When writing an application that accesses data in a database, the best
-practice is to use [repositories](Repositories.html) to encapsulate all
+practice is to use [repositories](Repositories.md) to encapsulate all
 data-access/persistence-related code. Other parts of the application
-(typically [controllers](Controllers.html)) can then depend on these
+(typically [controllers](Controllers.md)) can then depend on these
 repositories for data access. To test Repository dependents
 (for example, Controllers) in isolation, we need to provide a test double,
 usually as a test stub.