RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Documentation called "Encrypting Syslog Traffic with TLS (SSL)" (rsyslog_secure_tls.html) contains typos ("secrity" and "achived"):

"Our secrity goals are achived via public/private key security."

Version-Release number of selected component (if applicable):
rsyslog-5.8.10-7.el6_4.x86_64

How reproducible:
always

Steps to Reproduce:
1. open /usr/share/doc/rsyslog-5.8.10/rsyslog_secure_tls.html

Actual results:
contains typos

Expected results:
no typos

Additional info:
N/A

Created attachment 823496 [details]
proposed patch

Thanks for the patch.

I fear that there are actually many more typos in the docs and it wouldn't hurt for somebody to proofread them. It would certainly be more worthy of upstreams time to come to them with a larger change set.