diff --git a/ibmvstgt/src/Kconfig b/ibmvstgt/src/Kconfig
index bbf91aec6..f3f71155e 100644
--- a/ibmvstgt/src/Kconfig
+++ b/ibmvstgt/src/Kconfig
@@ -206,7 +206,7 @@ config SCSI_MULTI_LUN
 	  mobile phone in mass storage mode. This option forces the kernel to
 	  probe for all LUNs by default. This setting can be overriden by
 	  max_luns boot/module parameter. Note that this option does not affect
-	  devices conforming to SCSI-3 or higher as they can explicitely report
+	  devices conforming to SCSI-3 or higher as they can explicitly report
 	  their number of LUNs. It is safe to say Y here unless you have one of
 	  those rare devices which reacts in an unexpected way when probed for
 	  multiple LUNs.
diff --git a/ibmvstgt/src/orig/2.6.35/Kconfig b/ibmvstgt/src/orig/2.6.35/Kconfig
index 75f233680..d07f508d1 100644
--- a/ibmvstgt/src/orig/2.6.35/Kconfig
+++ b/ibmvstgt/src/orig/2.6.35/Kconfig
@@ -206,7 +206,7 @@ config SCSI_MULTI_LUN
 	  mobile phone in mass storage mode. This option forces the kernel to
 	  probe for all LUNs by default. This setting can be overriden by
 	  max_luns boot/module parameter. Note that this option does not affect
-	  devices conforming to SCSI-3 or higher as they can explicitely report
+	  devices conforming to SCSI-3 or higher as they can explicitly report
 	  their number of LUNs. It is safe to say Y here unless you have one of
 	  those rare devices which reacts in an unexpected way when probed for
 	  multiple LUNs.
diff --git a/ibmvstgt/src/orig/2.6.36/Kconfig b/ibmvstgt/src/orig/2.6.36/Kconfig
index bbf91aec6..f3f71155e 100644
--- a/ibmvstgt/src/orig/2.6.36/Kconfig
+++ b/ibmvstgt/src/orig/2.6.36/Kconfig
@@ -206,7 +206,7 @@ config SCSI_MULTI_LUN
 	  mobile phone in mass storage mode. This option forces the kernel to
 	  probe for all LUNs by default. This setting can be overriden by
 	  max_luns boot/module parameter. Note that this option does not affect
-	  devices conforming to SCSI-3 or higher as they can explicitely report
+	  devices conforming to SCSI-3 or higher as they can explicitly report
 	  their number of LUNs. It is safe to say Y here unless you have one of
 	  those rare devices which reacts in an unexpected way when probed for
 	  multiple LUNs.
diff --git a/qla2x00t/qla2x00-target/qla2x00t.c b/qla2x00t/qla2x00-target/qla2x00t.c
index ba7813af7..2d6f98112 100644
--- a/qla2x00t/qla2x00-target/qla2x00t.c
+++ b/qla2x00t/qla2x00-target/qla2x00t.c
@@ -5297,7 +5297,7 @@ static void q2t_response_pkt(scsi_qla_host_t *ha, response_t *pkt)
 					 * command was sent between the abort request
 					 * was received and processed. Unfortunately,
 					 * the firmware has a silly requirement that
-					 * all aborted exchanges must be explicitely
+					 * all aborted exchanges must be explicitly
 					 * terminated, otherwise it refuses to send
 					 * responses for the abort requests. So, we
 					 * have to (re)terminate the exchange and