diff --git a/Common/MemoryUtil.cpp b/Common/MemoryUtil.cpp
index 98ca6bcaab..8748067dde 100644
--- a/Common/MemoryUtil.cpp
+++ b/Common/MemoryUtil.cpp
@@ -303,7 +303,7 @@ void ProtectMemoryPages(const void* ptr, size_t size, uint32_t memProtFlags) {
 		if ((memProtFlags & (MEM_PROT_WRITE | MEM_PROT_EXEC)) == (MEM_PROT_WRITE | MEM_PROT_EXEC))
 			PanicAlert("Bad memory protect : W^X is in effect, can't both write and exec");
 	}
-	// Note - both VirtualProtect will affect the full pages containing the requested range.
+	// Note - VirtualProtect will affect the full pages containing the requested range.
 	// mprotect does not seem to, at least not on Android unless I made a mistake somewhere, so we manually round.
 #ifdef _WIN32
 	uint32_t protect = ConvertProtFlagsWin32(memProtFlags);
diff --git a/UI/GameSettingsScreen.cpp b/UI/GameSettingsScreen.cpp
index 856ab74e65..fea7d947ef 100644
--- a/UI/GameSettingsScreen.cpp
+++ b/UI/GameSettingsScreen.cpp
@@ -1109,17 +1109,8 @@ void DeveloperToolsScreen::CreateViews() {
 	list->Add(new ItemHeader(sy->T("General")));
 
 	bool canUseJit = true;
-#ifdef IOS
-	if (!iosCanUseJit) {
-		canUseJit = false;
-		if (targetIsJailbroken) {
-			// if the device is jailbroken and it's being marked as unable to JIT, then that means it must be arm64 iOS 9
-			list->Add(new TextView(sy->T("iOS9NoDynarec", "Dynarec (JIT) - (JIT not yet working on arm64 iOS 9)")));
-		} else {
-			list->Add(new TextView(sy->T("DynarecisJailed", "Dynarec (JIT) - (Not jailbroken - JIT not available)")));
-		}
-	}
-#endif
+	// iOS can now use JIT on all modes, apparently.
+	// The bool may come in handy for future non-jit platforms though (UWP XB1?)
 
 	static const char *cpuCores[] = { "Interpreter", "Dynarec (JIT)", "IR Interpreter" };
 	PopupMultiChoice *core = list->Add(new PopupMultiChoice(&g_Config.iCpuCore, gr->T("CPU Core"), cpuCores, 0, ARRAY_SIZE(cpuCores), sy->GetName(), screenManager()));