From 3939809366662dd473a6f9f0a65d9c1d2881d1ca Mon Sep 17 00:00:00 2001
From: meglynst <meglynst@users.noreply.github.com>
Date: Thu, 16 Nov 2023 20:07:24 +0000
Subject: [PATCH] squash! Prettier

---
 .../product/design/research/conducting-evaluative-research.md    | 1 -
 1 file changed, 1 deletion(-)

diff --git a/content/departments/product/design/research/conducting-evaluative-research.md b/content/departments/product/design/research/conducting-evaluative-research.md
index 74e4f9a05851..4c65d286fc98 100644
--- a/content/departments/product/design/research/conducting-evaluative-research.md
+++ b/content/departments/product/design/research/conducting-evaluative-research.md
@@ -34,4 +34,3 @@ To choose the right evaluative research method, you need to first identify your
 | <ul><li>Evaluate a change to a feature and/or process</li><li>Evaluate how well a current design supports user’s goals</li></ul>                                                                                    | <ul><li>[Usability testing](./usability-testing-how-to.md)</li></ul> |
 | <ul><li>Understand how the current information architecture performs</li><li>Learn if the current labels make sense to users</li><li>Learn if users can find the information they need easily and quickly</li></ul> | <ul><li>Card sorting</li><li>Tree testing</li></ul>                  |
 | <ul><li>Verify that the first click a user makes on an interface is the intended starting point for a given workflow or a navigation element</li></ul>                                                              | <ul><li>First click testing</li></ul>                                |
-