2
0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-30 14:07:59 +00:00

some tweaks for grammar and clarity

This commit is contained in:
Evan Hunt
2018-03-13 09:43:01 -07:00
committed by Ondřej Surý
parent 3686f141a3
commit 2df7134d69
2 changed files with 17 additions and 10 deletions

View File

@@ -1,38 +1,42 @@
<!--
If the bug you are reporting is security related or it does involve a crash in named, please do not fill it here, but send an email to [security-officer@isc.org](security-officer@isc.org).
If the bug you are reporting is potentially security-related - for example,
if it involves an assertion failure or other crash in `named` that can be
triggered repeatedly - then please do *NOT* report it here, but send an
email to [security-officer@isc.org](security-officer@isc.org).
-->
### Summary
(Summarize the bug encountered concisely)
(Summarize the bug encountered concisely.)
### Steps to reproduce
(How one can reproduce the issue - this is very important)
(How one can reproduce the issue - this is very important.)
### What is the current *bug* behavior?
(What actually happens)
(What actually happens.)
### What is the expected *correct* behavior?
(What you should see instead)
(What you should see instead.)
### Relevant configuration files
(Paste any relevant configuration files - please use code blocks (```)
to format console output, If submitting the contents of your
to format console output. If submitting the contents of your
configuration file in a non-confidential Issue, it is advisable to
obscure key secrets: this can be done automatically by using
`named-checkconf -px`.)
### Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
(Paste any relevant logs - please use code blocks (```) to format console
output, logs, and code, as it's very hard to read otherwise.)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
(If you can, link to the line of code that might be responsible for the
problem.)
/label ~bug

View File

@@ -1,3 +1,6 @@
### Security Issue
If the bug you are reporting is security related, please do not fill it here, but send an email to [security-officer@isc.org](security-officer@isc.org).
If the bug you are reporting is potentially security-related - for example,
if it involves an assertion failure or other crash in `named` that can be
triggered repeatedly - then please do *NOT* report it here, but send an
email to [security-officer@isc.org](security-officer@isc.org).