diff --git a/Tutorials/xsm_interrupts_tutorial.html b/Tutorials/xsm_interrupts_tutorial.html
index aa13e89..9715636 100644
--- a/Tutorials/xsm_interrupts_tutorial.html
+++ b/Tutorials/xsm_interrupts_tutorial.html
@@ -221,15 +221,16 @@
XSM Interrupts and Exception Handling
After the execution of each instruction in unprivileged mode, the machine checks whether a pending
-disk/console/timer interrupt. If so, the machine does the following actions:
+disk/console interrupt. If so, the machine does the following actions:
- *Push the IP value into the top of the stack.
-- Set IP to value stored in the interrupt vector table entry for the timer interrupt
- handler. The vector table entry for timer interrupt is located at physical address 493 in page 0
- (ROM) of XSM and the value 2048 is preset in this location. Hence, the IP register gets value
- 2048. The machine then switches to to privileged mode and address translation is disabled.
- Hence, next instruction will be fetched from physical address 2048. (See Boot ROM and Boot block section in XSM Machine Organisation documentation)
+- Set IP to value stored in the interrupt vector table entry for the corresponding interrupt
+ handler. The vector table entry for disk interrupt is located at physical address 494 in page 0
+ (ROM) of XSM and the value 3072 is preset in this location and for console interrupt is located at physical address 495 in page 0
+ (ROM) of XSM and the value 4096 is preset in this location. Hence, the IP register gets value
+ 3072 for disk interrupt and 4096 for console interrupt. The machine then switches to privileged mode and address translation is disabled.
+ Hence, next instruction will be fetched from physical address 3072 for disk interrupt and 4096 for console interupt. (See Boot ROM and Boot block section in XSM Machine Organisation documentation)
*Note: If the value in the SP register after incrementing SP is an invalid address (i.e., not in the
range 0 to PTLR*512-1) then the machine generates an illegal memory access exception (see section below on exception handling). The machine will re-execute steps (1) and (2) immedietly after retrun to unprivileged mode, before executing any other instruction in unprivileged mode.