diff --git a/documentation/docs/bitloops-language/how-to-guides/define-a-dto.md b/documentation/docs/bitloops-language/how-to-guides/define-a-dto.md
index d1460989..509b5264 100644
--- a/documentation/docs/bitloops-language/how-to-guides/define-a-dto.md
+++ b/documentation/docs/bitloops-language/how-to-guides/define-a-dto.md
@@ -38,4 +38,4 @@ DTO HExampleResponseDTO {
 
 By default, all parameters are required (unless optional is used in front) and errors will be thrown in the controllers if parameters are missing.  
 
-To learn more about DTOs, read our reference guide on [DTOs](https://bitloops.com/docs/bitloops-language/reference/dto)
+To learn more about DTOs, read this reference guide on [DTOs](https://stackoverflow.com/questions/1051182/what-is-a-data-transfer-object-dto)
diff --git a/documentation/docs/bitloops-language/how-to-guides/define-an-entity.md b/documentation/docs/bitloops-language/how-to-guides/define-an-entity.md
index ca242c69..c683e5a6 100644
--- a/documentation/docs/bitloops-language/how-to-guides/define-an-entity.md
+++ b/documentation/docs/bitloops-language/how-to-guides/define-an-entity.md
@@ -18,7 +18,7 @@ Entity TitleEntity {
   }
 ```
 
-Now, in Bitloops Language specifically, to ensure good coding practice, there is the concept of [Root Entity](https://bitloops.com/docs/bitloops-language/reference/entity). This is a special type of Entity as its the Entity that can be referenced by other objects in the application. 
+Now, in Bitloops Language specifically, to ensure good coding practice, there is the concept of Root Entity. This is a special type of Entity as its the Entity that can be referenced by other objects in the application. 
 
 To declare this type of Entity, you should simply add Root as a prefix: 
 
diff --git a/documentation/docs/bitloops-language/learning/software-design/behavior-driven-development.md b/documentation/docs/bitloops-language/learning/software-design/behavior-driven-development.md
index e0ec6008..b695b520 100644
--- a/documentation/docs/bitloops-language/learning/software-design/behavior-driven-development.md
+++ b/documentation/docs/bitloops-language/learning/software-design/behavior-driven-development.md
@@ -59,7 +59,7 @@ E. Boost productivity: BDD enhances productivity in the code development process
 By incorporating BDD into the software development process, teams can benefit from improved collaboration, reduced risks, streamlined focus, better communication, and boosted productivity. These benefits ultimately lead to a higher quality product that meets the needs of both the business and the end-users.
 
 
-## Key differences between traditional software development and behavior-driven development
+## Traditional software development vs  BDD
 
 In traditional development process, the business owner conveys the software requirements to the product developer, who drafts a requirement document that is then shared with the developer and tester. The focus is on writing codes and test cases, and after executing the tests, changes are made and retesting is performed until the final product is delivered. However, in this process, the developers and testers are not involved in understanding the system's behavior, leading to potential miscommunication and errors in the final product.