Fixed broken links

_docs-2/administration/in-depth-install.md

@@ -103,9 +103,8 @@ manually or run `accumulo-cluster create-config`.
 
 Logging is configured in [accumulo-env.sh] to use three log4j configuration files in `conf/`. The
 file used depends on the Accumulo command or service being run. Logging for most Accumulo services
-(i.e. Manager, TabletServer, Garbage Collector) is configured by [log4j-service.properties] except for
-the Monitor which is configured by [log4j-monitor.properties]. All Accumulo commands (i.e `init`,
-`shell`, etc) are configured by [log4j.properties].
+(i.e. Manager, TabletServer, Garbage Collector) is configured by [log4j2-service.properties]. All Accumulo commands (i.e `init`,
+`shell`, etc) are configured by [log4j2.properties].
 
 ### Configure accumulo-env.sh
 
@@ -521,7 +520,7 @@ set by `ACCUMULO_LOG_DIR` in [accumulo-env.sh].
 
 Accumulo logs many user-initiated actions, and whether they succeeded or failed, to an slf4j logger
 named `org.apache.accumulo.audit`. This logger can be configured in the user's logging framework
-(such as log4j or logback). In the tarball, the configuration file `conf/log4j-service.properties`
+(such as log4j or logback). In the tarball, the configuration file `conf/log4j2-service.properties`
 demonstrates basic audit logging with example configuration options for log4j.
 
 ## Recovery
@@ -753,6 +752,7 @@ Please check the release notes for your Accumulo version or use the
 [monitor.port.log4j]: {% purl monitor.port.log4j %}
 [monitor.port.client]: {% purl monitor.port.client %}
 [tserver.port.client]: {% purl tserver.port.client %}
+[sserver.port.client]: {% purl sserver.port.client %}
 [gc.port.client]: {% purl gc.port.client %}
 [manager.port.client]: {% purl manager.port.client %}
 [trace.port.client]: {% purl trace.port.client %}
@@ -775,9 +775,9 @@ Please check the release notes for your Accumulo version or use the
 [accumulo-client.properties]: {% durl configuration/files#accumulo-clientproperties %}
 [gc]: {% durl configuration/files#gc %}
 [monitor-host]: {% durl configuration/files#monitor %}
-[manager]: {% durl configuration/files#managers %}
-[tserver]: {% durl configuration/files#tservers %}
+[manager]: {% durl configuration/files#manager %}
+[tserver]: {% durl configuration/files#tserver %}
 [tracers]: {% durl configuration/files#tracers %}
-[log4j-service.properties]: {% durl configuration/files#log4j-serviceproperties %}
+[log4j2-service.properties]: {% durl configuration/files#log4j2-serviceproperties %}
 [log4j-monitor.properties]: {% durl configuration/files#log4j-monitorproperties %}
-[log4j.properties]: {% durl configuration/files#log4jproperties %}
+[log4j2.properties]: {% durl configuration/files#log4j2properties %}

_docs-2/administration/upgrading.md

@@ -21,7 +21,7 @@ The basic upgrade sequence is:
   configure it in your environment
 - start ZooKeeper and HDFS.
 - (optional - but recommended) create a ZooKeeper snapshot
-- (optional - but recommended) validate the ZooKeeper ACLs. See [ZooKeeper ACLs]({% durl troubleshooting/ZooKeeper#ACLs %})
+- (optional - but recommended) validate the ZooKeeper ACLs. See [ZooKeeper ACLs]({% durl troubleshooting/zookeeper#zookeeper-acls %})
 - (required if not using the provided scripts to start 2.1) run the `RenameMasterDirInZK` utility
 - (optional) run the pre-upgrade utility to convert the configuration in ZooKeeper
 - start Accumulo 2.1 for the first time to complete the upgrade

_docs-2/configuration/server-properties.md

@@ -119,6 +119,7 @@ Below are properties set in `accumulo.properties` or the Accumulo shell that con
 | <a name="monitor_prefix" class="prop"></a> **monitor.*** | **Available since:** 1.3.5<br>Properties in this category affect the behavior of the monitor web server. |
 | <a name="monitor_lock_check_interval" class="prop"></a> monitor.lock.check.interval | **Available since:** 1.5.1<br>The amount of time to sleep between checking for the Monitor ZooKeeper lock<br>**type:** TIMEDURATION, **zk mutable:** no, **default value:** `5s` |
 | <a name="monitor_port_client" class="prop"></a> monitor.port.client | **Available since:** 1.3.5<br>The listening port for the monitor's http service<br>**type:** PORT, **zk mutable:** no, **default value:** `9995` |
+| <a name="monitor_port_log4J" class="prop"></a> monitor.port.log4j | **Available since:** 1.3.5<br>The listening port for the monitor's http service<br>**type:** PORT, **zk mutable:** no, **default value:** `9995` |
 | <a name="monitor_resources_external" class="prop"></a> monitor.resources.external | **Available since:** 2.0.0<br>A JSON Map of Strings. Each String should be an HTML tag of an external resource (JS or CSS) to be imported by the Monitor. Be sure to wrap with CDATA tags. If this value is set, all of the external resources in the `<head>` tag of the Monitor will be replaced with the tags set here. Be sure the jquery tag is first since other scripts will depend on it. The resources that are used by default can be seen in accumulo/server/monitor/src/main/resources/templates/default.ftl<br>**type:** STRING, **zk mutable:** no, **default value:** empty |
 | <a name="monitor_ssl_exclude_ciphers" class="prop"></a> monitor.ssl.exclude.ciphers | **Available since:** 1.6.1<br>A comma-separated list of disallowed SSL Ciphers, see monitor.ssl.include.ciphers to allow ciphers<br>**type:** STRING, **zk mutable:** no, **default value:** empty |
 | <a name="monitor_ssl_include_ciphers" class="prop"></a> monitor.ssl.include.ciphers | **Available since:** 1.6.1<br>A comma-separated list of allows SSL Ciphers, see monitor.ssl.exclude.ciphers to disallow ciphers<br>**type:** STRING, **zk mutable:** no, **default value:** empty |