#2278 Improve getting started docs

docs/v2/getting-started/a-post-archive.md

@@ -31,7 +31,7 @@ You can then loop over your posts with a [for-loop in Twig](https://twig.symfony
         <ul>
     {% endif %}
 
-	{{ include('pagination.twig') }}
+    {{ include('pagination.twig') }}
 {% endblock %}
 ```
 
@@ -45,6 +45,9 @@ Your teaser could look like this. We used the markup for an [Inclusive Card](htt
 <img
     src="{{ post.thumbnail.src('medium') }}"
     alt="{{ post.thumbnail.alt }}"
+    width="{{ post.thumbnail.width }}"
+    height="{{ post.thumbnail.height }}"
+    loading="lazy"
 >
 
 <h2>
@@ -71,7 +74,7 @@ There are two new things that you see here:
 
 ## Using custom queries
 
-Sometimes you’ll want to use your own queries for archive pages or to display a list of posts in other places. For that, you can use `Timber::get_posts()`. Here’s an example for a more complex query, that selects posts that have certain movie genre and actor terms assigned. The parameters you use are the same as those for [WP_Query](https://developer.wordpress.org/reference/classes/wp_query/).
+Sometimes you’ll want to use your own queries for archive pages or to display a list of posts in other places. For that, you can use `Timber::get_posts()`. Here’s an example for a more complex query, that selects posts that have certain movie genres and actor terms assigned. The parameters you use are the same as those for [WP_Query](https://developer.wordpress.org/reference/classes/wp_query/).
 
 ```php
 $args = [
@@ -111,6 +114,7 @@ $post = $context['post'];
 $context['related_posts'] = Timber::get_posts([
     'post_type' => 'post',
     'posts_per_page' => 3,
+    'no_found_rows' => true,
     'orderby' => 'date',
     'order' => 'DESC',
     'post__not_in' => [$post->ID],

docs/v2/getting-started/introduction.md

@@ -89,7 +89,7 @@ See how there’s no HTML in our PHP file? And do you see how we fetch the data
 
 In Timber, we prepare a lot for you in the background, so you don’t have to remember function names like `get_the_title()`.
 
-Most of Timber’s templates look like this:
+Most Timber templates look like this:
 
 **index.php**
 

docs/v2/getting-started/template-inheritance-and-includes.md

@@ -101,11 +101,11 @@ For this introduction, let’s assume that the name of the page is "All about Ja
             {% block headline %}
                 <header>
                     <h1 class="article-title">{{ post.title }}</h1>
-                    <p role="doc-subtitle">{{ post.subtitle }}</h2>
+                    <p role="doc-subtitle">{{ post.subtitle }}</p>
                 </header>
             {% endblock %}
 
-            <p class="article-author"><span>By</span> {{ post.author.name }} <span>&bull;</span> {{ post.post_date }}</p>
+            <p class="article-author"><span>By</span> {{ post.author.name }} <span>&bull;</span> {{ post.date }}</p>
 
             {{ post.content }}
         </section>
@@ -141,7 +141,7 @@ So there are two big concepts going on here:
 1. **Multiple Inheritance:** We’re extending **single.twig**, which itself extends **base.twig**. Thus we stay true to the [DRY](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself) principle and don’t have very similar code between our two templates hanging around.
 2. **Nested Blocks:** `{% block headline %}` is located inside `{% block content %}`. So while we’re replacing the headline, we get to keep all the other markup and variables found in the parent template.
 
-What if you wanted to **add** something to the block as opposed to replace? In this case you can [`{{ parent() }}`](https://twig.symfony.com/doc/functions/parent.html) where the parent block’s content should go.
+What if you wanted to **add** something to the block as opposed to replace? In this case you can use [`{{ parent() }}`](https://twig.symfony.com/doc/functions/parent.html) where the parent block’s content should go.
 
 ```twig
 {% extends "single.twig" %}