From 0b4924214f48ba38b28d5079a138a350856c47b0 Mon Sep 17 00:00:00 2001
From: greenart7c3 <115044884+greenart7c3@users.noreply.github.com>
Date: Sat, 31 Aug 2024 07:37:02 -0300
Subject: [PATCH] Update 55.md

Co-authored-by: dluvian <133484344+dluvian@users.noreply.github.com>
---
 55.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/55.md b/55.md
index adcbb44a..4d751f14 100644
--- a/55.md
+++ b/55.md
@@ -442,7 +442,7 @@ If the user chose to always reject the event, signer application will return the
 
 # Usage for Web Applications
 
-You should consider using [NIP-46: Nostr Connect](46.md), [Nostr login](https://github.com/nostrband/nostr-login) or (window.nostr.js)[https://github.com/fiatjaf/window.nostr.js] for a better experience for web applications. When using this approach the web app can't call the signer in background so the user will see a popup for every event you try to sign.
+You should consider using [NIP-46: Nostr Connect](46.md), [Nostr login](https://github.com/nostrband/nostr-login) or [window.nostr.js](https://github.com/fiatjaf/window.nostr.js) for a better experience for web applications. When using this approach, the web app can't call the signer in the background, so the user will see a popup for every event you try to sign.
 
 Since web applications can't receive a result from the intent, you should add a modal to paste the signature or the event json or create a callback url.