From 297019c6706c8c27a58717f0a4269abf92af8de4 Mon Sep 17 00:00:00 2001
From: Stephan Schroevers <stephan.schroevers@teampicnic.com>
Date: Mon, 26 Feb 2024 09:25:40 -0800
Subject: [PATCH] Fix some mistakes in the EnumOrdinal examples

PiperOrigin-RevId: 610431336
---
 docs/bugpattern/EnumOrdinal.md | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/docs/bugpattern/EnumOrdinal.md b/docs/bugpattern/EnumOrdinal.md
index ae3ab68f363..e934408fd15 100644
--- a/docs/bugpattern/EnumOrdinal.md
+++ b/docs/bugpattern/EnumOrdinal.md
@@ -9,16 +9,18 @@ Prefer using enum value directly:
 ImmutableMap<MyEnum, String> MAPPING =
     ImmutableMap.<MyEnum, String>builder()
         .put(MyEnum.FOO, "Foo")
-        .put(MyEnum.BAR, "Bar");
+        .put(MyEnum.BAR, "Bar")
+        .buildOrThrow();
 ```
 
 to this:
 
 ```java
- ImmutableMap<Integer, String> MAPPING =
-    ImmutableMap.<MyEnum, String>builder()
+ImmutableMap<Integer, String> MAPPING =
+    ImmutableMap.<Integer, String>builder()
         .put(MyEnum.FOO.ordinal(), "Foo")
-        .put(MyEnum.BAR.ordinal(), "Bar");
+        .put(MyEnum.BAR.ordinal(), "Bar")
+        .buildOrThrow();
 ```
 
 Or if you need a stable number for serialisation, consider defining an explicit