fix another typo

Author: MSIH

README.md

@@ -107,7 +107,7 @@ For Windows:
 
 5\. Follow section Securing access to Active Directory servers to enable LDAPS
 
-Disaster recovery: In case that after all of this you cannot login anymore, you should enable the logging on the plugin to understand why it is failing. In case that after you enable the secured option you cannot login on the instance anymore, you might want to quickly fallback to the previous status specially on production environments. You can easily do this by going to $JENKINS\_HOME/config.xml and under the section \<securityRealm class="hudson.plugins.active.directory.ActiveDirectorySecurityRealm" revert the tlsConfiguration to the previous status. A restart is needed.
+Disaster recovery: In case that after all of this you cannot login anymore, you should enable the logging on the plugin to understand why it is failing. In case that after you enable the secured option you cannot login on the instance anymore, you might want to quickly fallback to the previous status specially on production environments. You can easily do this by going to $JENKINS\_HOME/config.xml and under the section \<securityRealm class="hudson.plugins.active_directory.ActiveDirectorySecurityRealm" revert the tlsConfiguration to the previous status. A restart is needed.
 
     <tlsConfiguration>TRUST_ALL_CERTIFICATES</tlsConfiguration>
 
@@ -188,7 +188,7 @@ If you are not sure what the notation for a group name is, try the following pro
 
 #### Create/Update a dedicated Logs Recorder
 
-If you think you've configured everything correctly but still not being able to login (or any other problems), please enable [Logging](https://www.jenkins.io/doc/book/system-administration/viewing-logs/) and configure logging level for "hudson.plugins.active\_directory" to ALL. Attempt a login and then file a ticket with the log output.
+If you think you've configured everything correctly but still not being able to login (or any other problems), please enable [Logging](https://www.jenkins.io/doc/book/system-administration/viewing-logs/) and configure logging level for "hudson.plugins.active_directory" to ALL. Attempt a login and then file a ticket with the log output.
 
 Also, it might be useful to enable: