PeriodicPrizeStrategy - Inconsistent behavior between award-phase modifiers and view functions
The logic in the `canStartAward()` function is inconsistent with that of the `requireCanStartAward` modifier, and the logic in the `canCompleteAward()` function is inconsistent with that of the `requireCanCompleteAward` modifier. Neither of these view functions appear to be used elsewhere in the codebase, but the similarities between the function names and the corresponding modifiers is highly misleading.\\n`canStartAward()` is inconsistent with `requireCanStartAward`\\n```\\nfunction canStartAward() external view returns (bool) {\\n  return \\_isPrizePeriodOver() && !isRngRequested();\\n}\\n```\\n\\n```\\nmodifier requireCanStartAward() {\\n  require(\\_isPrizePeriodOver(), "PeriodicPrizeStrategy/prize-period-not-over");\\n  require(!isRngRequested() || isRngTimedOut(), "PeriodicPrizeStrategy/rng-already-requested");\\n  \\_;\\n}\\n```\\n\\n`canCompleteAward()` is inconsistent with `requireCanCompleteAward`\\n```\\nfunction canCompleteAward() external view returns (bool) {\\n  return isRngRequested() && isRngCompleted();\\n}\\n```\\n\\n```\\nmodifier requireCanCompleteAward() {\\n  require(\\_isPrizePeriodOver(), "PeriodicPrizeStrategy/prize-period-not-over");\\n  require(isRngRequested(), "PeriodicPrizeStrategy/rng-not-requested");\\n  require(isRngCompleted(), "PeriodicPrizeStrategy/rng-not-complete");\\n  \\_;\\n}\\n```\\n
Make the logic consistent between the view functions and the modifiers of the same name or remove the functions.
```\\nfunction canStartAward() external view returns (bool) {\\n  return \\_isPrizePeriodOver() && !isRngRequested();\\n}\\n```\\n