From 12e31acbc9e09b1711730d1363100a3aed6c2a8c Mon Sep 17 00:00:00 2001
From: Tomoaki Mizushima <31090417+chachamimm@users.noreply.github.com>
Date: Wed, 31 Jan 2024 15:02:25 +0900
Subject: [PATCH] Update HOWTO.md

---
 HOWTO.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/HOWTO.md b/HOWTO.md
index e8d1de88..01cfb7aa 100644
--- a/HOWTO.md
+++ b/HOWTO.md
@@ -16,8 +16,6 @@ I'd propose the following flow to manage the feedback from brainstorming discuss
 Who gave what kind of ideas about what topic during the call?
 1. How to deal with GitHub Issues/PRs?
     * McCool: would like to suggest we look at proposal from ege/toumura regarding user stories before we dive into the template, may need multiple templates
-        * https://github.com/w3c/wot-usecases/issues/257#issuecomment-1907308039
-        * https://github.com/w3c/wot-usecases/issues/261
 2. How to extract information, e.g., about requirements, from the UC description?
     * McCool: we should also think about how to extract information from the use case description.
         * we should extract user story as well