Fix some very minor spelling mistakes

Found by Lintian https://lintian.debian.org/
This commit is contained in:
James Cowgill 2016-02-19 01:48:10 +00:00
parent 1f2b1caf42
commit db8dbae131
5 changed files with 5 additions and 5 deletions

View File

@ -1182,7 +1182,7 @@ void GekkoDisassembler::ps_mem(u32 inst)
} }
// Disassemble PPC instruction and return a pointer to the next // Disassemble PPC instruction and return a pointer to the next
// instruction, or nullptr if an error occured. // instruction, or nullptr if an error occurred.
u32* GekkoDisassembler::DoDisassembly(bool big_endian) u32* GekkoDisassembler::DoDisassembly(bool big_endian)
{ {
u32 in = *m_instr; u32 in = *m_instr;

View File

@ -257,7 +257,7 @@ void DSPLLE::DSP_WriteMailBoxHigh(bool _CPUMailbox, u16 _uHighMail)
{ {
if (gdsp_mbox_peek(MAILBOX_CPU) & 0x80000000) if (gdsp_mbox_peek(MAILBOX_CPU) & 0x80000000)
{ {
ERROR_LOG(DSPLLE, "Mailbox isnt empty ... strange"); ERROR_LOG(DSPLLE, "Mailbox isn't empty ... strange");
} }
#if PROFILE #if PROFILE

View File

@ -187,7 +187,7 @@ void SetInterrupt(u32 _causemask, bool _bSet)
else else
m_InterruptCause &= ~_causemask;// is there any reason to have this possibility? m_InterruptCause &= ~_causemask;// is there any reason to have this possibility?
// F|RES: i think the hw devices reset the interrupt in the PI to 0 // F|RES: i think the hw devices reset the interrupt in the PI to 0
// if the interrupt cause is eliminated. that isnt done by software (afaik) // if the interrupt cause is eliminated. that isn't done by software (afaik)
UpdateException(); UpdateException();
} }

View File

@ -925,7 +925,7 @@ bool NetPlayServer::initUPnP()
#endif #endif
if (!devlist) if (!devlist)
{ {
WARN_LOG(NETPLAY, "An error occured trying to discover UPnP devices."); WARN_LOG(NETPLAY, "An error occurred trying to discover UPnP devices.");
m_upnp_error = true; m_upnp_error = true;
m_upnp_inited = false; m_upnp_inited = false;

View File

@ -143,7 +143,7 @@ void StateCache::Init()
{ {
// If a PSO fails to create, that means either: // If a PSO fails to create, that means either:
// - The file itself is corrupt. // - The file itself is corrupt.
// - A driver/HW change has occured, causing the existing cache blobs to be invalid. // - A driver/HW change has occurred, causing the existing cache blobs to be invalid.
// //
// In either case, we want to re-create the disk cache. This should not be a frequent occurence. // In either case, we want to re-create the disk cache. This should not be a frequent occurence.