In this case for soft-fork, it change the consensus rules that require those who proceed blocks to agree with the changes, but the update is reversible. As long as Majority of the user apply the updated consensus rules, the original blockchain will not be "Fork"(Recreate/Split).
But in the case of Hard-fork, All the user are REQUIRE to implement the new consensus rule towards the chain else a "Fork" (Split Chain) will happen?
Therefore, for the segwit update, it can be 80% of user to process block with the segwit updated core chain and the leftover 20% to process block without the segwit package?
Sorry if my words sounds confusing because english is not my native so hope you got me
Understanding why SegWit is a soft-fork change and not a hard fork change requires understanding some of the technical details about how SegWit was implemented. This can cause some confusion since you are trying to understand 2 things at the same time (How does SegWit work? AND Why is that a soft-fork?).
Perhaps it would be better to use a more simple example of soft-fork and hard-fork to better understand what it means when something is a soft-fork. We will not talk about "Core" or "Unlimited" or "SegWit" or any of the current future plans. We will just talk about a simple change that would be a fork.
Example:
There is currently a limit on the MAXIMUM size of a block. A block cannot be bigger than 1 Megabyte.
If any miner tries to make a bigger block, then ALL bitcoin software (other miners, nodes, wallets, exchanges, etc) will just ignore that block. The miner will have wasted time, money, and effort creating junk that nobody else accepts as part of bitcoin.
If any miner tries to make a smaller block, then ALL bitcoin software (other miners, nodes, wallets, exchanges, etc) will accept that block. The block will be added to everybody's blockchain and the miner will receive the reward (subsidy plus transaction fees) that he pays to himself.
If we want to allow a larger 2 megabyte MAXIMUM block size, it will require that EVERYBODY implement that change at the same time. If, instead, some miners, and/or some nodes, and/or some wallets, and/or some exchanges, etc implement the change to accept 2 megabyte blocks, and others don't implement the change, then when a miner creates a larger block, some of the network will accept it and add it to their chain, and others will not. Imagine that ONE miner doesn't change to the new software, and ALL the other miners do. 99.999% of the hash power is running new software and is able to accept bigger 2 megabyte blocks. Imagine also that ONLY YOU change to the new software. 99.999% of all other users (nodes, wallets, exchanges, etc) are still running old software and NOT able to accept bigger 2 megabyte blocks. Now imagine that one of the MANY miners creates a block that is 1.1 megabytes in size. The ONE miner that isn't running the new software won't accept this block. It will appear to be "invalid". That ONE miner will create his own separate and completely different block 0.9 megabyte block. Since YOU are running the new software, YOU will accept the bigger 1.1 megabyte block and will see transactions and confirmations from the 1.1 megabyte block. EVERYONE ELSE will ignore that block (since their software says that block is "invalid"). They will ALL accept the smaller 0.9 megabyte block and will see transactions and confirmations from the 0.9 megabyte block. Prior to the creation of this bigger block, we all agree on which transactions exist, and which are confirmed. Now (after the bigger block is created) there is no longer agreement. This is a HARD FORK. The changes look invalid to the old software. Therefore, the chain splits and anyone on the old software (even just one person) sees different information than anyone on the new software. Notice that even though almost ALL the miners and almost ALL the hashpower is willing to accept the new bigger blocks, they are unable to get the old software (and anyone using that old software) to accept this new higher MAXIMUM.
If we want to restrict to a smaller 0.5 megabyte MAXIMUM block size, it will only require that a significant majority of miners agree. If a minority of miners don't upgrade, and if none of the non-mining users upgrade, then the majority hashpower CAN enforce the rule on everybody else. Imagine that ONE miner doesn't change to the new software, and ALL the other miners do. That one miner is still willing to accept blocks bigger than 0.5 megabytes (up to 1 megabyte). 99.999% of the hash power is running new software and is refusing to accept blocks bigger than 0.5 megabytes. Imagine also that ONLY YOU change to the new software and so you will refuse to accept blocks bigger than 0.5 megabytes. 99.999% of all other users (nodes, wallets, exchanges, etc) are still running old software and are still willing to accept the old bigger blocks (up to 1 megabyte). Now imagine that one of the MANY miners running the new software creates a block that is 0.5 megabytes in size. The ONE miner that isn't running the new software WILL accept this block since it is less than 1 megabyte in size. It will appear to be "valid". Since YOU are running the new software, YOU will accept this smaller 0.5 megabyte block but so will All the other users that accept anything up to 1 megabyte. Notice that the new software is still compatible with the old software. Anything that is less than 0.5 megabytes is ALSO smaller than 1 megabyte. Now imagine that the ONLY miners running the old software creates a block that is 0.9 megabytes in size. Momentarily there will be a split since YOU and all the other hash power will treat this block as "INVALID". However, since the MAJORITY of the hashpower is running the new software, they will create blocks faster than that one miner. Eventually their chain will grow to be longer that the chain being built by that one miner. Since that longer chain is a "valid" chain according to the rules of those running the old software, they will abandon their short chain with the bigger 0.9 megabyte block and will switch over to the longer valid chain with all blocks smaller than 0.5 megabytes. This is a SOFT FORK. The changes look valid to the old software. Therefore if the minority of hashpower ever splits the chain, the greater hashpower will eventually create a longer valid chain that will replace the split and enforce the new rules on anyone running the old software.