From bb0e4dea79bece06bdc7a479d34b716924137912 Mon Sep 17 00:00:00 2001
From: Tom Snee <351700+tsnee@users.noreply.github.com>
Date: Sun, 3 Mar 2024 11:20:51 -0500
Subject: [PATCH] Fix numbering conflict in methods-main-methods.md.

---
 _overviews/scala3-book/methods-main-methods.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/_overviews/scala3-book/methods-main-methods.md b/_overviews/scala3-book/methods-main-methods.md
index 02d40cc225..b56fd5a2d9 100644
--- a/_overviews/scala3-book/methods-main-methods.md
+++ b/_overviews/scala3-book/methods-main-methods.md
@@ -123,8 +123,8 @@ The Scala compiler generates a program from an `@main` method `f` as follows:
 
 For instance, the `happyBirthday` method above generates additional code equivalent to the following class:
 
-{% tabs method_3 %}
-{% tab 'Scala 3 Only' for=method_3 %}
+{% tabs method_4 %}
+{% tab 'Scala 3 Only' for=method_4 %}
 
 ```scala
 final class happyBirthday {
@@ -158,7 +158,7 @@ The previous functionality of `App`, which relied on the “magic” `DelayedIni
 
 If programs need to cross-build between Scala 2 and Scala 3, it’s recommended to use an `object` with an explicit `main` method and a single `Array[String]` argument instead:
 
-{% tabs method_4 %}
+{% tabs method_5 %}
 {% tab 'Scala 2 and 3' %}
 
 ```scala