diff --git a/Source/pSys/ReadMe.txt b/Source/pSys/ReadMe.txt
index 9c1c5507..749a38ed 100644
--- a/Source/pSys/ReadMe.txt
+++ b/Source/pSys/ReadMe.txt
@@ -48,7 +48,7 @@ The layout of the first track does not conform exactly to the
 recommended p-System layout.  The recommended layout is not possible 
 because it conflicts with the RomWBW definition for a boot track.  
 However, the changes are only slightly different sector assignments for 
-the different boot componets -- the general boot sequence and mechanism 
+the different boot components -- the general boot sequence and mechanism 
 for the p-System is completely standard.
 
 The logical disk geometry used by this p-System
@@ -77,14 +77,17 @@ escape sequence handling configuration.  The debugger code as added to
 SYSTEM.PASCAL to enable the debug function.  SYSTEM.INTERP was modified 
 to enable the extended BIOS functions.
 
-The build/makefile creates the psys disk image (psys.img) by adding 
-concatentating psys.vol and blank.vol (after adding track 0 contents to 
+The build/makefile creates the psys disk image (psys.img) by 
+concatenating psys.vol and blank.vol (after adding track 0 contents to 
 each).  psys.vol and blank.vol are recognized by CiderPress and 
 CiderPress can be used to add/remove files from these volumes.  
-However, there is currently no straightforward way to extract the 
-volumes from the disk image.  If you are good with a binary disk 
-editor, you can do it that way.  Please contact me if you are 
-interested in pursuing that.
+To extract volumes from a disk image, Andrew Davidson has created
+a nice Python script that can extract p-System volumes from an
+existing disk image file.  The extracted volume can be manipulated
+by CiderPress.  The script is also capable of re-inserting a modified
+volume back into the disk image file.  This tool is available at:
+https://github.com/robosnacks/psysimg.
+
 
 There is currently no support for floppy drives.
 
@@ -119,7 +122,7 @@ that SofTech produced a IV.1 with some nice enhancements (like
 subsidiary volumes and decent support for ANSI/VT-100 terminals).  I
 have been unable to track down the IV.1 distribution media despite
 trying very hard.  If anyone knows of a source for the media of the
-Adapable p-System for Z80, I would love to get hold of it.
+Adaptable p-System for Z80, I would love to get hold of it.
 
 3:58 PM Tuesday, January 17, 2023
 
@@ -138,4 +141,10 @@ arrow keys transmitted by an ANSI/VT-100 terminal.  In this case,
 the setup program was used to define up/down/left/right like
 WordStar does: ^E,^X,^S,^D.
 
-5:48 PM Tuesday, January 17, 2023
\ No newline at end of file
+5:48 PM Tuesday, January 17, 2023
+
+Updated instructions above to include a reference to Andrew 
+Davidson's Python script that will extract/insert volumes from/to
+a disk image.
+
+1:31 PM Thursday, May 11, 2023
\ No newline at end of file
diff --git a/Source/pSys/psys.vol b/Source/pSys/psys.vol
index 358175d3..9d0db099 100644
Binary files a/Source/pSys/psys.vol and b/Source/pSys/psys.vol differ
diff --git a/Source/ver.inc b/Source/ver.inc
index 6874ad01..70ceab46 100644
--- a/Source/ver.inc
+++ b/Source/ver.inc
@@ -2,7 +2,7 @@
 #DEFINE	RMN	3
 #DEFINE	RUP	0
 #DEFINE	RTP	0
-#DEFINE BIOSVER	"3.3.0-dev.13"
+#DEFINE BIOSVER	"3.3.0-dev.14"
 #define rmj	RMJ
 #define rmn	RMN
 #define rup	RUP
diff --git a/Source/ver.lib b/Source/ver.lib
index a9ef6aa7..41a88ab5 100644
--- a/Source/ver.lib
+++ b/Source/ver.lib
@@ -3,5 +3,5 @@ rmn	equ	3
 rup	equ	0
 rtp	equ	0
 biosver	macro
-	db	"3.3.0-dev.13"
+	db	"3.3.0-dev.14"
 	endm