docs: update docker-systemd-general.md #2420
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For this statement: "Make it a habit to check back here regularly to be sure any changes that may have been made to the template unit file below" is there a more concrete way to say this? I feel like the customer is going to be confused about how often they are expected to check back in. is it with every release?
@jenworthington that's a good point. In fact this file hasn't been changed for at least 8 months but I would still say that it's a good practice to check with every upgrade of SC4S on the customer side |
|
@jenworthington ready for the final pass |
Incorporated feedback and made more style edits.
mstopa-splunk
changed the title
|
🎉 This PR is included in version 3.23.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For this statement: "Make it a habit to check back here regularly to be sure any changes that may have been made to the template unit file below" is there a more concrete way to say this? I feel like the customer is going to be confused about how often they are expected to check back in. is it with every release?