fix: fix issue #11 typo

Author: xflcx1991

README.md

@@ -10,7 +10,7 @@ There are two relay servers available, one in Washington (WA), one in Shanghai.
 - `relay.aosc.io`: IPv4 only, routed via [Microsoft global network](https://learn.microsoft.com/azure/networking/microsoft-global-network), **developers outside of China** should choose this. Connect to this server with `ssh <buildbot>`.
 - `relay-ipv6.aosc.io`: IPv6 only, routed via Microsoft global network, **developers outside of China with IPv6** should choose this. Connect to this server with `ssh <buildbot>-ipv6`.
 - `relay-cn.aosc.io`: IPv4 only, routed via Microsoft global network, **developers in China** should choose this. Connect to this server with `ssh <buildbot>-cn`.
-- `relay-cn-ipv6.aosc.io`: IPv4 only, routed via Microsoft global network, **developers in China with IPv6** should choose this. Connect to this server with `ssh <buildbot>-cn-ipv6`.
+- `relay-cn-ipv6.aosc.io`: IPv6 only, routed via Microsoft global network, **developers in China with IPv6** should choose this. Connect to this server with `ssh <buildbot>-cn-ipv6`.
 - `relay-inet.aosc.io`: IPv4 only, [routed over public Internet (ISP network)](https://learn.microsoft.com/azure/virtual-network/ip-services/routing-preference-overview#routing-over-public-internet-isp-network), **suitable for only specific cases**, such as outage with Microsoft global network. Connect to this server with `ssh <buildbot>-inet`.
 
 Some but not all buildbots are directly accessible from public Internet. These configurations are also included. Works best if the developer is geographically (and digitally) nearby. Connect with `ssh <buildbot>-direct`.