From b859eb8243c4a9e7a6d0d20bdf58363c3a9bcbfa Mon Sep 17 00:00:00 2001 From: Oliver Dvorski Date: Fri, 11 Feb 2022 11:27:22 +0100 Subject: [PATCH] Fix typos and add clarity --- docs/api/wrapper/findComponent.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api/wrapper/findComponent.md b/docs/api/wrapper/findComponent.md index febbb41e3..99172e98f 100644 --- a/docs/api/wrapper/findComponent.md +++ b/docs/api/wrapper/findComponent.md @@ -26,7 +26,7 @@ expect(barRef.exists()).toBe(true) ``` ::: warning Usage with CSS selectors -Using `findAllComponents` with CSS selector might have confusing behavior +Using `findComponent` with a CSS selector might have confusing behavior Consider this example: @@ -50,5 +50,5 @@ const childByCss = wrapper.findComponent('.child') expect(childByCss.vm.$options.name).toBe('Root') // => still Root ``` -The reason for such behavior is that `RootComponent` and `ChildComponent` are sharing same DOM node and only first matching component is included for each unique DOM node +The reason for such behavior is that `RootComponent` and `ChildComponent` are sharing the same DOM node and only the first matching component is returned for each unique DOM node :::