Minor changes should be thoroughly documented and follow some type of standard cadence, as this can help maintain the audit trail and visibility of the changes. All changes should still be tested, even if they are minor, as they can have unexpected impacts on other parts of the system or introduce bugs or security issues. Downstream environments will not be automatically updated when production changes are made, so it is important to have a strategy to keep them in sync and avoid conflicts or overwrites. Minor changes do not need to be documented and can be made at any time is a wrong statement, as it can lead to poor governance and lack of accountability. CI/CD is not required to successfully manage minor changes, although it can help automate and streamline the process. See Application Lifecycle and Deployment for more details.