grammar: may be

maybe be -- does not really make sense, it should almost always be
written as simply: may be.
This commit is contained in:
Josh Soref
2016-09-16 02:40:19 +00:00
parent 6992a6479a
commit 552640506e
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -9,7 +9,7 @@ We use the following labels for issue classifications:
* `Issue-Bug`: the issue is reporting a bug
* `Issue-Discussion`: the issue may not have a clear classification yet.
The issue may generate an [RFC][ln-rfc] or maybe be reclassified as a bug or enhancement.
The issue may generate an [RFC][ln-rfc] or may be reclassified as a bug or enhancement.
* `Issue-Enhancement`: the issue is more of a feature request than a bug.
* `Issue-Meta`: an issue used to track multiple issues.
* `Issue-Question`: ideally support can be provided via other mechanisms,
@@ -321,7 +321,7 @@ namespace Microsoft.PowerShell
// get corresponding scan code
uint scanCode = NativeMethods.MapVirtualKey(virtualKey, NativeMethods.MAPVK_VK_TO_VSC);
// get corresponding character - maybe be 0, 1 or 2 in length (diacritics)
// get corresponding character - may be 0, 1 or 2 in length (diacritics)
var chars = new char[2];
int charCount = NativeMethods.ToUnicode(
virtualKey, scanCode, state, chars, chars.Length, NativeMethods.MENU_IS_INACTIVE);