From 06ad859bb2789e2819919d2d275ea021b84f3c2b Mon Sep 17 00:00:00 2001
From: Daniel Ehrenberg <dehrenberg@bloomberg.net>
Date: Sun, 31 Mar 2024 14:57:11 -0400
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index a90d8be..0977fd4 100644
--- a/README.md
+++ b/README.md
@@ -1,10 +1,10 @@
 # 🚦 JavaScript Signals standard proposal🚦
+<img align=right src="signals-logo.png" alt="Signals logo" width=300 height=300>
+
 Stage 0
 
 Authors: Rob Eisenberg and Daniel Ehrenberg
 
-<img align=right src="signals-logo.png" alt="Signals logo" width=300 height=300>
-
 This document describes an early common direction for signals in JavaScript, similar to the Promises A+ effort which preceded the Promises standardized by TC39 in ES2015. Try it for yourself, using [a polyfill](https://github.com/proposal-signals/proposal-signals/tree/main/packages/signal-polyfill).
 
 Similarly to Promises A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of [Angular](https://angular.io/), [Bubble](https://bubble.io/), [Ember](https://emberjs.com/), [FAST](https://www.fast.design/), [MobX](https://mobx.js.org/), [Preact](https://preactjs.com/), [Qwik](https://qwik.dev/), [RxJS](https://rxjs.dev/), [Solid](https://www.solidjs.com/), [Starbeam](https://www.starbeamjs.com/), [Svelte](https://svelte.dev/), [Vue](https://vuejs.org/), Wiz, and more…