updated the docs

Author: Raramuri

docs/advanced-guide/circuit-breaker/page.md

@@ -23,12 +23,12 @@ import (
 func main() {
 	// Create a new application
 	app := gofr.New()
-	
+
 	app.AddHTTPService("order", "https://order-func",
 		&service.CircuitBreakerConfig{
 		    // Number of consecutive failed requests after which circuit breaker will be enabled
 			Threshold: 4,
-			// Time interval at which circuit breaker will hit the aliveness endpoint.  
+			// Time interval at which circuit breaker will hit the aliveness endpoint.
 			Interval:  1 * time.Second,
 		},
 	)
@@ -41,6 +41,6 @@ func main() {
 ```
 
 Circuit breaker state changes to open when number of consecutive failed requests increases the threshold.
-When it is in open state, GoFr makes request to the aliveness endpoint (default being -  /.well-known/alive) at an equal interval of time provided in config.
+When it is in open state, GoFr makes request to the aliveness endpoint (default being - /.well-known/alive) at an equal interval of time provided in config.
 
-To override the default aliveness endpoint {% new-tab-link title="refer" href="/docs/advanced-guide/monitoring-service-health" /%}.
+To override the default aliveness endpoint {% new-tab-link newtab=false title="refer" href="/docs/advanced-guide/monitoring-service-health" /%}.

docs/advanced-guide/handling-data-migrations/page.md

@@ -1,7 +1,7 @@
 # Handling Data Migrations
 
 Suppose you manually make changes to your database, and now it's your responsibility to inform other developers to execute them. Additionally, you need to keep track of which changes should be applied to production machines in the next deployment.
-Gofr supports data migrations for MySQL, Postgres and Redis which allows to alter the state of a database, be it adding a new column to existing table or modifying the data type of  existing column or adding constraints to an existing table, setting and removing keys etc.
+Gofr supports data migrations for MySQL, Postgres and Redis which allows to alter the state of a database, be it adding a new column to existing table or modifying the data type of existing column or adding constraints to an existing table, setting and removing keys etc.
 
 ## Usage
 
@@ -11,12 +11,13 @@ It is recommended to maintain a migrations directory in your project root to enh
 
 **Migration file names**
 
-It is recommended that each migration file should be numbered in the format of *YYYYMMDDHHMMSS* when the migration was created.
+It is recommended that each migration file should be numbered in the format of _YYYYMMDDHHMMSS_ when the migration was created.
 This helps prevent numbering conflicts and allows for maintaining the correct sort order by name in different filesystem views.
 
 Create the following file in migrations directory.
 
 **Filename : 20240226153000_create_employee_table.go**
+
 ```go
 package migrations
 
@@ -45,14 +46,15 @@ func createTableEmployee() migration.Migrate {
 }
 ```
 
-`migration.Datasource` have the datasources whose migrations are supported i.e. Redis and SQL (MySQL and PostgreSQL). 
+`migration.Datasource` have the datasources whose migrations are supported i.e. Redis and SQL (MySQL and PostgreSQL).
 All the migrations always run in a transaction.
 
 For MySQL it is highly recommended to use `IF EXISTS` and `IF NOT EXIST` in DDL commands as MySQL implicitly commits these commands.
 
 **Create a function which returns all the migrations in a map**
 
 **Filename : all.go**
+
 ```go
 package migrations
 
@@ -67,7 +69,8 @@ func All() map[int64]migration.Migrate {
 
 Migrations will run in ascending order of keys in this map.
 
-### Initialisation from main.go 
+### Initialisation from main.go
+
 ```go
 package main
 
@@ -95,11 +98,8 @@ When we run the app we will see the following logs for migrations which ran succ
 INFO [16:55:46] Migration 20240226153000 ran successfully
 ```
 
-
-
-
 GoFr maintains the records in the database itself which helps in tracking which migrations have already been executed and ensures that only migrations that have never been run are executed.
-This way, you only need to ensure that your migrations are properly in place. {% new-tab-link title="Learn more" href="https://cloud.google.com/architecture/database-migration-concepts-principles-part-1" /%}
+This way, you only need to ensure that your migrations are properly in place. {% new-tab-link  title="Learn more" href="https://cloud.google.com/architecture/database-migration-concepts-principles-part-1" /%}
 
 ## Migration Records
 
@@ -108,21 +108,32 @@ This way, you only need to ensure that your migrations are properly in place. {%
 Migration records are stored and maintained in **gofr_migrations** table which has the following schema:
 
 {% table %}
-* Field
-* Type
+
+- Field
+- Type
+
 ---
-* version
-* bigint
+
+- version
+- bigint
+
 ---
-* method
-* varchar(4)
+
+- method
+- varchar(4)
+
 ---
-* start_time
-* timestamp
+
+- start_time
+- timestamp
+
 ---
-* duration
-* bigint
+
+- duration
+- bigint
+
 ---
+
 {% /table %}
 
 **REDIS**

docs/advanced-guide/http-communication/page.md

@@ -1,32 +1,37 @@
 # Interservice HTTP Calls
+
 GoFr promotes microservice architecture and to facilitate the same, it provides the support
 to initialize HTTP services at application level using `AddHTTPService()` method.
 Support for inter-service http calls provide the following benefits:
 
 1. Access to the method from container - GET, PUT, POST, PATCH, DELETE.
 2. Logs and traces for the request.
-3. {% new-tab-link title="Circuit breaking" href="/docs/advanced-guide/circuit-breaker" /%} for enhanced resilience and fault tolerance.
-4. {% new-tab-link title="Custom Health Check" href="/docs/advanced-guide/monitoring-service-health" /%} Endpoints
+3. {% new-tab-link newtab=false title="Circuit breaking" href="/docs/advanced-guide/circuit-breaker" /%} for enhanced resilience and fault tolerance.
+4. {% new-tab-link newtab=false title="Custom Health Check" href="/docs/advanced-guide/monitoring-service-health" /%} Endpoints
 
 ## Usage
 
 ### Registering a simple HTTP Service
-Users can register a new HTTP service using the application method `AddHTTPService()`. 
+
+Users can register a new HTTP service using the application method `AddHTTPService()`.
 It takes in a service name and service address argument to register your dependent service at application level.
 Users can easily register multiple dependent services easily, which is a common use case in a microservice architecture.
+
 > The services instances are maintained by the container.
 
-Users can provide other options additionally to coat their basic http client with features like circuit-breaker and 
+Users can provide other options additionally to coat their basic http client with features like circuit-breaker and
 custom health check to add to the functionality of the HTTP service.
 The design choice for this was made so that user can add as many options as required and are order agnostic,
 i.e. the order of the options is not important.
+
 > Service names are to be kept unique to one service.
 
 ```go
 app.AddHTTPService(<service_name> , <service_address>)
 ```
 
 #### Example
+
 ```go
 package main
 
@@ -49,6 +54,7 @@ func main() {
 ```
 
 ### Accessing HTTP Service in handler
+
 Users can access the HTTP service client from anywhere using the gofr.Context that gets passed on from the handler.
 The service name that was given at the time of registering the service.
 
@@ -58,22 +64,22 @@ svc := ctx.GetHTTPService(<service_name>)
 
 ```go
 func Customer(ctx *gofr.Context) (interface{}, error) {
-    // Get the payment service client 
+    // Get the payment service client
     paymentSvc := ctx.GetHTTPService("payment")
-	
+
 	// Use the Get method to call the GET /user endpoint of payments service
 	resp, err := paymentSvc.Get(ctx, "user", nil)
     if err != nil {
         return nil, err
     }
-	
+
 	defer resp.Body.Close()
-	
+
     body, err := io.ReadAll(resp.Body)
     if err != nil {
         return nil, err
     }
-    
+
     return string(body), nil
 }
 ```