Tweak a couple of words in my blog post

On first reading post-publish, couple of things stood out.
This commit is contained in:
Dave Pearson
2022-11-27 08:33:29 +00:00
parent b0111d9c9c
commit 61ad39661b

View File

@@ -175,7 +175,7 @@ is going to be really useful.
## unbored ## unbored
The next application was initially going to be a very quick hack, but The next application was initially going to be a very quick hack, but
actually turned into a less-trivial build that I'd initially envisaged; not actually turned into a less-trivial build than I'd initially envisaged; not
in a negative way though. The more I played with it the more I explored and in a negative way though. The more I played with it the more I explored and
I feel that this ended up being my first really good exploration of some I feel that this ended up being my first really good exploration of some
useful (personal -- your kilometerage may vary) patterns and approaches when useful (personal -- your kilometerage may vary) patterns and approaches when
@@ -218,7 +218,7 @@ It was easy enough to do, and I had an action in the `Main` screen that
with some `if`/`elif` work but it didn't feel elegant. Moreover, it meant with some `if`/`elif` work but it didn't feel elegant. Moreover, it meant
that the `Footer` always displayed the same description for the key. that the `Footer` always displayed the same description for the key.
That's when I realised that it made way more sense to have a `BINDING` for That's when I realised that it made way more sense to have a `Binding` for
`escape` in every widget that was the actual context for escape's use. So I `escape` in every widget that was the actual context for escape's use. So I
went from one top-level binding to... went from one top-level binding to...