docs: fix subset field typo (#961)

docs/en/latest/references/apisix_route_v2beta3.md

@@ -47,7 +47,7 @@ Meaning of each field in the spec of ApisixRoute are followed, the top level fie
 | http[].backends[].servicePort | integer or string | The backend service port, can be the port number or the name defined in the service object.
 | http[].backends[].resolveGranularity | string | See [Service Resolve Granularity](#service-resolve-granularity) for the details.
 | http[].backends[].weight | int | The backend weight, which is critical when shifting traffic between multiple backends, default is `100`. Weight is ignored when there is only one backend.
-| http[].backends[].subnet | string | Subset specifies a subset for the target Service. The subset should be pre-definedin ApisixUpstream about this service.
+| http[].backends[].subset | string | Subset specifies a subset for the target Service. The subset should be pre-definedin ApisixUpstream about this service.
 | http[].plugins | array | A series of APISIX plugins that will be executed once this route rule is matched |
 | http[].plugins[].name | string | The plugin name, see [docs](http://apisix.apache.org/docs/apisix/getting-started) for learning the available plugins.
 | http[].plugins[].enable | boolean | Whether the plugin is in use |

test/e2e/README.md

@@ -68,6 +68,6 @@ How to name test cases
 Because we use `ginkgo --focus` option and the prefix `suite-<suite name>` to split test cases and make them run in parallel in CI, test cases should be named in the following way:
 
 - All test cases are grouped by directories, and **their names should have `suite-` prefix**
-- All top level specs (i.e. `ginkgo.Describe`) under the suite directory should have corresponding `suite-<suite-name>: ` prefix.
+- All top level specs (i.e. `ginkgo.Describe`) under the suite directory should have corresponding `suite-<suite-name>:` prefix.
 
 Run `make names-check` to check the above naming convention.