[hotfix] Fix typo: excepted -> expected and sever->server (#1557)

Author: beryllw

fluss-common/src/main/java/com/alibaba/fluss/cluster/Endpoint.java

@@ -40,7 +40,7 @@
 /**
  * Endpoint is what fluss server is listened for. It includes host, port and listener name. Listener
  * name is used for routing, all the fluss servers can have the same listener names to listen. For
- * example, coordinator server and tablet sever can use internal listener to communicate with each
+ * example, coordinator server and tablet server can use internal listener to communicate with each
  * other. And If a client connect to a server with a host and port, it can only see the other
  * server's same listener.
  */

fluss-rpc/src/main/java/com/alibaba/fluss/rpc/protocol/Errors.java

@@ -150,7 +150,7 @@ public enum Errors {
     STORAGE_EXCEPTION(26, "The general storage exception.", StorageException::new),
     OPERATION_NOT_ATTEMPTED_EXCEPTION(
             27,
-            "The sever did not attempt to execute this operation.",
+            "The server did not attempt to execute this operation.",
             OperationNotAttemptedException::new),
     NOT_ENOUGH_REPLICAS_AFTER_APPEND_EXCEPTION(
             28,

fluss-server/src/test/java/com/alibaba/fluss/server/kv/snapshot/KvSnapshotDataUploaderTest.java

@@ -106,11 +106,11 @@ void testMultiThreadUploadCorrectly() throws Exception {
 
     private void assertContentEqual(Path stateFilePath, FSDataInputStream inputStream)
             throws IOException {
-        byte[] excepted = Files.readAllBytes(stateFilePath);
-        byte[] actual = new byte[excepted.length];
+        byte[] expected = Files.readAllBytes(stateFilePath);
+        byte[] actual = new byte[expected.length];
         IOUtils.readFully(inputStream, actual, 0, actual.length);
         assertThat(inputStream.read()).isEqualTo(-1);
-        assertThat(actual).isEqualTo(excepted);
+        assertThat(actual).isEqualTo(expected);
     }
 
     private List<Path> generateRandomSstFiles(

website/community/how-to-contribute/contribute-code.md

@@ -49,7 +49,7 @@ Considerations before opening a pull request:
 
 - Make sure that the pull request corresponds to a [GitHub issue](https://github.com/alibaba/fluss/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no issue.
 
-- Name the pull request in the format "[component] Title of the pull request", where *[component]* should be replaced by the name of the component being changed. Typically, this corresponds to the component label assigned to the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are unsure about which is the best component. **Hotfixes** should be named for example `[hotfix][docs] Expand JavaDoc for PuncuatedWatermarkGenerator`.
+- Name the pull request in the format "[component] Title of the pull request", where *[component]* should be replaced by the name of the component being changed. Typically, this corresponds to the component label assigned to the issue (e.g., [kv], [log], [client], [flink]). Skip *[component]* if you are unsure about which is the best component. **Hotfixes** should be named for example `[hotfix][docs] Expand JavaDoc for PunctuatedWatermarkGenerator`.
 
 - Fill out the pull request template to describe the changes contributed by the pull request. Please describe it such that the reviewer understands the problem and solution from the description, not only from the code. That will give reviewers the context they need to do the review.