bullet point formatting, fixing content paths

1 files changed, 3 insertions, 2 deletions

diff --git a/source/blog/yaxpeax.md b/source/blog/yaxpeax.md
index 9f8cc88..9c2d925 100644
--- a/source/blog/yaxpeax.md
+++ b/source/blog/yaxpeax.md
@@ -18,6 +18,7 @@ even this, it seems, is enough to have a twinkle of promise!!
 * [for disassembly](https://github.com/novafacing/tsffs/blob/10697a078ab5510127bd7c067760e2f8cb593675/tsffs_module/src/processor/mod.rs#L743-L751) in part of a coverage-guided fuzzer
 
 and in some uses of my own - of course i find nails for my hammer:
+
 * [yaxpeax-dis](https://github.com/iximeow/yaxpeax-dis), as a "please try to disassemble this" tool, including all\* yaxpeax-supporting disassemblers
   \* "all" meaning best effort :)
 * [dis.yaxpeax.net](https://dis.yaxpeax.net), same as the above, but as a website
@@ -27,10 +28,10 @@ and in some uses of my own - of course i find nails for my hammer:
 
 but the real place i hope to find yaxpeax one day is to be used for analysis tasks like
 
-![register numbering](register_numbering.png)\  
+![register numbering](yaxpeax/register_numbering.png)\  
 
 constructing an SSA-style representation of machine code, in turn letting me (or you!!!) get value anlyses,
 
-![range inference](range_inference.png)\  
+![range inference](yaxpeax/range_inference.png)\  
 
 anyway, between Then and Now.. Ghidra has become an entire *thing*. Binary Ninja still exists and continues improving. maybe yaxpeax ends up just a pile of neat disassemblers and toys demos in my (ha ha) spare time.