diff --git a/docs/book/src/SUMMARY.md b/docs/book/src/SUMMARY.md
index a2eb8a02ae0..d664e6bdf2f 100644
--- a/docs/book/src/SUMMARY.md
+++ b/docs/book/src/SUMMARY.md
@@ -69,7 +69,7 @@
       - [Migration by updating the files](migration/legacy/manually_migration_guide_v2_v3.md)
   - [From v3.0.0 with plugins](./migration/v3-plugins.md)
     - [go/v3 vs go/v4-alpha](migration/v3vsv4.md)
-    
+
       - [Migration Guide](migration/migration_guide_gov3_to_gov4.md)
       - [Migration by updating the files](migration/manually_migration_guide_gov3_to_gov4.md)
   - [Single Group to Multi-Group](./migration/multi-group.md)
diff --git a/docs/book/src/migration/manually_migration_guide_gov3_to_gov4.md b/docs/book/src/migration/manually_migration_guide_gov3_to_gov4.md
index e776bb5beb9..87172effcf2 100644
--- a/docs/book/src/migration/manually_migration_guide_gov3_to_gov4.md
+++ b/docs/book/src/migration/manually_migration_guide_gov3_to_gov4.md
@@ -16,14 +16,14 @@ The recommended upgrade approach is to follow the [Migration Guide go/v3 to go/v
 
 ## Migration from project config version "go/v3" to "go/v4"
 
-Update the `PROJECT` file layout which stores information about the resources that are used to enable plugins make 
+Update the `PROJECT` file layout which stores information about the resources that are used to enable plugins make
 useful decisions while scaffolding. The `layout` field indicates the scaffolding and the primary plugin version in use.
 
 ### Steps to migrate
 
 #### Migrate the layout version into the PROJECT file
 
-The following steps describe the manual changes required to bring the project configuration file (`PROJECT`). 
+The following steps describe the manual changes required to bring the project configuration file (`PROJECT`).
 These change will add the information that Kubebuilder would add when generating the file. This file can be found in the root directory.
 
 Update the PROJECT file by replacing:
@@ -64,7 +64,7 @@ Therefore, you can check the changes in the layout results into:
 
 - Create a new directory `cmd` and move the `main.go` under it.
 - If your project support multi-group the APIs are scaffold under a directory called `apis`. Rename this directory to `api`
-- Move the `controllers` directory under the `internal` and rename it for `controller` 
+- Move the `controllers` directory under the `internal` and rename it for `controller`
 - Now ensure that the imports will be updated accordingly by:
   - Update the `main.go` imports to look for the new path of your controllers under the `pkg` directory
 
@@ -136,17 +136,17 @@ Note that if your project has multiple groups (`multigroup:true`) then the above
 The PROJECT tracks the paths of all APIs used in your project. Ensure that they now point to `api/...` as the following example:
 
 Before update:
-  group: crew
-  kind: Captain
-  path: sigs.k8s.io/kubebuilder/testdata/project-v4/apis/crew/v1
+group: crew
+kind: Captain
+path: sigs.k8s.io/kubebuilder/testdata/project-v4/apis/crew/v1
 ```
 
 After Update:
 
 ```
-  group: crew
-  kind: Captain
-  path: sigs.k8s.io/kubebuilder/testdata/project-v4/api/crew/v1
+group: crew
+kind: Captain
+path: sigs.k8s.io/kubebuilder/testdata/project-v4/api/crew/v1
 ```
 
 ### Update kustomize manifests with the changes made so far
diff --git a/docs/book/src/migration/v3vsv4.md b/docs/book/src/migration/v3vsv4.md
index 403b21411ac..9c97674a75a 100644
--- a/docs/book/src/migration/v3vsv4.md
+++ b/docs/book/src/migration/v3vsv4.md
@@ -20,8 +20,8 @@ The details of all changes (breaking or otherwise) can be found in:
 - no longer scaffold webhook test files with `"k8s.io/api/admission/v1beta1"` the k8s API which is no longer served since k8s `1.25`. By default
   webhooks test files are scaffolding using `"k8s.io/api/admission/v1"` which is support from k8s `1.20`
 - no longer provide backwards compatible support with k8s versions < `1.16`
-- change the layout to accommodate the community request to follow the [Standard Go Project Layout][standard-go-project] 
-by moving the api(s) under a new directory called `api`, controller(s) under a new directory called `internal` and the `main.go` under a new directory named `cmd`
+- change the layout to accommodate the community request to follow the [Standard Go Project Layout][standard-go-project]
+  by moving the api(s) under a new directory called `api`, controller(s) under a new directory called `internal` and the `main.go` under a new directory named `cmd`
 
 <aside class="note">
 <H1> TL;DR of the New `go/v4-alpha` Plugin </H1>
diff --git a/docs/book/src/plugins/creating-plugins.md b/docs/book/src/plugins/creating-plugins.md
index 463e0d3b433..d04e34f2090 100644
--- a/docs/book/src/plugins/creating-plugins.md
+++ b/docs/book/src/plugins/creating-plugins.md
@@ -58,9 +58,9 @@ In this way, currently, you can [Extend the CLI][extending-cli] and use the `Bun
 
 ```go
   mylanguagev1Bundle, _ := plugin.NewBundle(language.DefaultNameQualifier, plugin.Version{Number: 1},
-		kustomizecommonv1.Plugin{}, // extend the common base from Kubebuilder
-		mylanguagev1.Plugin{}, // your plugin language which will do the scaffolds for the specific language on top of the common base
-	)
+kustomizecommonv1.Plugin{}, // extend the common base from Kubebuilder
+mylanguagev1.Plugin{}, // your plugin language which will do the scaffolds for the specific language on top of the common base
+)
 ```
 
 If you do not want to develop your plugin using Golang, you can follow its standard by using the binary as follows:
@@ -170,9 +170,9 @@ Alternatively, you can create a plugin bundle to include the target plugins. For
 
 ```go
   mylanguagev1Bundle, _ := plugin.NewBundle(language.DefaultNameQualifier, plugin.Version{Number: 1},
-        kustomizecommonv1.Plugin{}, // extend the common base from Kuebebuilder
-        mylanguagev1.Plugin{}, // your plugin language which will do the scaffolds for the specific language on top of the common base
-    )
+kustomizecommonv1.Plugin{}, // extend the common base from Kuebebuilder
+mylanguagev1.Plugin{}, // your plugin language which will do the scaffolds for the specific language on top of the common base
+)
 ```
 
 [controller-runtime]: https://github.com/kubernetes-sigs/controller-runtime
diff --git a/docs/book/src/plugins/go-v4-plugin.md b/docs/book/src/plugins/go-v4-plugin.md
index 8f2a98b9fca..7fe046cc583 100644
--- a/docs/book/src/plugins/go-v4-plugin.md
+++ b/docs/book/src/plugins/go-v4-plugin.md
@@ -1,16 +1,16 @@
 # go/v4-alpha (go.kubebuilder.io/v4-alpha)
 
-Kubebuilder will scaffold using the `go/v4-alpha` plugin only if specified when initializing the project. 
-This plugin is a composition of the plugins ` kustomize.common.kubebuilder.io/v2-alpha` and `base.go.kubebuilder.io/v4-alpha`. 
-It scaffolds a project template that helps in constructing sets of [controllers][controller-runtime]. 
+Kubebuilder will scaffold using the `go/v4-alpha` plugin only if specified when initializing the project.
+This plugin is a composition of the plugins ` kustomize.common.kubebuilder.io/v2-alpha` and `base.go.kubebuilder.io/v4-alpha`.
+It scaffolds a project template that helps in constructing sets of [controllers][controller-runtime].
 
-It scaffolds boilerplate code to create and design controllers. 
+It scaffolds boilerplate code to create and design controllers.
 Note that by following the [quickstart][quickstart] you will be using this plugin.
 <aside class="note">
 
 <h1>Examples</h1>
 
-You can check samples using this plugin by looking at the `project-v4-<options>` projects 
+You can check samples using this plugin by looking at the `project-v4-<options>` projects
 under the [testdata][testdata] directory on the root directory of the Kubebuilder project.
 
 </aside>
@@ -24,8 +24,8 @@ under the [testdata][testdata] directory on the root directory of the Kubebuilde
 - If you are looking to have your project update with the latest version available
 - if you are not targeting k8s versions < `1.16` and `1.20` if you are using webhooks
 - If you are looking to work on with scaffolds which are compatible with k8s `1.25+`
-- If you are looking for the new layout following the [Standard Go Project Layout][standard-go-project] where 
-the "api(s)" are scaffold under the `api` directory, "controller(s)" under `internal`, and the `main.go` under `cmd`
+- If you are looking for the new layout following the [Standard Go Project Layout][standard-go-project] where
+  the "api(s)" are scaffold under the `api` directory, "controller(s)" under `internal`, and the `main.go` under `cmd`
 
 <aside class="note">