Deployed cdb4de3 with MkDocs version: 1.0.4

Trainer/Training Loop/index.html

@@ -616,7 +616,7 @@
                 
                   <h1>Training Loop</h1>
                 
-                <p>The lightning training loop handles everything except the actual computations of your model. To decide what will happen in your training loop, define the <a href="../../Pytorch-lightning/LightningModule/#training_step">training_step function</a>.</p>
+                <p>The lightning training loop handles everything except the actual computations of your model. To decide what will happen in your training loop, define the <a href="https://williamfalcon.github.io/pytorch-lightning/LightningModule/RequiredTrainerInterface/#training_step">training_step function</a>.</p>
 <p>Below are all the things lightning automates for you in the training loop.</p>
 <hr />
 <h4 id="accumulated-gradients">Accumulated gradients</h4>

Trainer/Validation loop/index.html

@@ -588,7 +588,7 @@
                 
                   <h1>Validation loop</h1>
                 
-                <p>The lightning validation loop handles everything except the actual computations of your model. To decide what will happen in your validation loop, define the <a href="../../Pytorch-lightning/LightningModule/#validation_step">validation_step function</a>.
+                <p>The lightning validation loop handles everything except the actual computations of your model. To decide what will happen in your validation loop, define the <a href="https://williamfalcon.github.io/pytorch-lightning/LightningModule/RequiredTrainerInterface/#validation_step">validation_step function</a>.
 Below are all the things lightning automates for you in the validation loop.</p>
 <p><strong>Note</strong> <br />
 Lightning will run 5 steps of validation in the beginning of training as a sanity check so you don't have to wait until a full epoch to catch possible validation issues.</p>