diff --git a/README.md b/README.md
index 555fc6cc2e903..5cadafc7745bc 100644
--- a/README.md
+++ b/README.md
@@ -66,7 +66,7 @@ Over 340,000 developers use [Lightning Cloud](https://lightning.ai/?utm_source=p
 
 # Why PyTorch Lightning?   
 
-Training models in plain PyTorch is tedious and error-prone - you have to manually handle things like backprop, mixed precision, multi-GPU, and distributed training, often rewriting code for every new project. PyTorch Lightning organizes PyTorch code to automate those complexities so you can focus on your model and data, while keeping full control and scaling from CPU to multi-node without changing your core code. But if you want control of those things, you can still opt into [expert-level control](#lightning-fabric-expert-contro).   
+Training models in plain PyTorch is tedious and error-prone - you have to manually handle things like backprop, mixed precision, multi-GPU, and distributed training, often rewriting code for every new project. PyTorch Lightning organizes PyTorch code to automate those complexities so you can focus on your model and data, while keeping full control and scaling from CPU to multi-node without changing your core code. But if you want control of those things, you can still opt into [expert-level control](#lightning-fabric-expert-control).   
 
 Fun analogy: If PyTorch is Javascript, PyTorch Lightning is ReactJS or NextJS.