From c152f73ebe93be7f87aa2262d08b26d6af5d3e69 Mon Sep 17 00:00:00 2001
From: Matteo Mirk <polaretto@gmail.com>
Date: Tue, 7 Mar 2023 13:00:38 +0100
Subject: [PATCH] corrected incongruent code in "Object mock"

---
 README.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 463aa84bf..1ca4e1958 100644
--- a/README.md
+++ b/README.md
@@ -381,13 +381,13 @@ every { ObjBeingMocked.add(1, 2) } returns 55
 assertEquals(55, ObjBeingMocked.add(1, 2))
 ```
 
-To revert back, use `unmockkAll` or `unmockkObject`:
+To revert back, use `unmockkObject` or `unmockkAll` (more destructive: cancels object, static and constructor mocks)
 
 ```kotlin
 @Before
 fun beforeTests() {
     mockkObject(ObjBeingMocked)
-    every { MockObj.add(1,2) } returns 55
+    every { ObjBeingMocked.add(1,2) } returns 55
 }
 
 @Test
@@ -397,14 +397,14 @@ fun willUseMockBehaviour() {
 
 @After
 fun afterTests() {
-    unmockkAll()
-    // or unmockkObject(ObjBeingMocked)
+    unmockkObject(ObjBeingMocked)
+    // or unmockkAll()
 }
 ```
 
 Despite the Kotlin language restrictions, you can create new instances of objects if required by testing logic:
 ```kotlin
-val newObjectMock = mockk<MockObj>()
+val newObjectMock = mockk<ObjBeingMocked>()
 ```
 
 ### Class mock