Update README.md

Author: DeveloperTryingToCodeLikeOtherOfThem

README.md

@@ -13,55 +13,13 @@ This repository can be added as an **extension** in MakeCode.
 
 This repository is meant for explaining how to code the engine in Microsoft MakeCode Arcade. This package does **NOT** connect to MakeCode's offical runtime docs, it is for local and to access the docs, you view the documentation here. 
 
-This can work properly by clicking the doc and seeing any of the .md files or go to your local MakeCode website and searching for this teaching extension and then view the files in the bottom of the explorer tab which you will see it say this extensions title, and then finding the md file by clicking the dropdown menu in the right of the title and the release (the number in the right of the title which has 2 decimals between all 3 digits). You would also see a trash can between both, please do not click it because it would permantly delete the extension in your editor to access. 
-
-The only way to get the extension back is by using this extension's link and pasting it back to the extensions tab and browsing the extension so you can read any docs in the extension again. This repository has been updated 
-and now **not** supported in any PXT target for documentation. It is now a repository you can view **only** in this repository. I did this mainily
-because there were many cached issues and limitations of how MakeCode parses and stores huge packaged files. So now if you want to view this repository,you view it **only** here.
-
 ## Support
 This extension **does not** work in any MakeCode editor because of the issues that were encountered in pxt.json. 
 Because of that, you have to review everything here instead. Also, tags and releases will still be updated, so do **not** worry about that. If you have any questions about this repository, please click on this link here. [Issues: Click Here](https://github.com/DeveloperTryingToCodeLikeOtherOfThem/pxt-hardware-programming-docs/issues). Please do **not** worry if you have questions because it is part of this repository too.
 
-## Preparation
-
-Be prepared because this repository might have different tone on the docs
-compared to the offical MakeCode docs. But, you will still have the documentations
-on what the function, property, etc. does.
-
-## ~~Procedures To Be Aware Of~~
-~~Updating Could Destroy Your Imported Extension: **Warning**, do not refresh the release of the package because it could break multiple files, so just avoid updating the release. The safest way to
-have the version updated in case if the extension has been updated again, just paste the link of this repository into the extension's link to make it safer for the latest version of this package.~~
- 
-~~Here is an image of the thing I recommend to **not** click.
-<img width="96" height="32" alt="image" src="https://github.com/user-attachments/assets/8b78d665-f095-4e8f-aa79-b51eaa59d124" />~~
-
-~~This happens if you did click on it.
-![Screen recording 2026-03-05 9 41 48 PM](https://github.com/user-attachments/assets/3ce2f31e-3d2b-485c-838a-85529e61e2f1)~~
-
-~~There are times when it is safe to update, but it depends. For example, there are many times where the best option to update without needing
-to import the extension again by clicking on a file that does not exist on another version and the other version does support it, which often
-MakeCode never made the version release back to an older version. It is still safer to not do it.~~
-
-~~Most of the users might cannot even access this repository in Microsoft MakeCode right now anyways, the only way to see is by seeing this respoitory instead.~~
-
-~~Here is something that you might see.~~
-
-~~![Screen recording 2026-03-06 12 22 32 AM](https://github.com/user-attachments/assets/a26fdcc6-121f-4476-b1da-6994b78ba431)~~
-
-~~I did fix the issue anyway, but if it persists, please make an issue here so you can tell me the bugs you found.~~
-
-~~Another way you could be able to avoid this error is by going to the pxt.json file (**Not Recommended**) for the version history itself there. You can tell where it is by
-seeing 2 decimals with a ones, tenths, and hundreths digit.~~
-
-~~<img width="786" height="17" alt="image" src="https://github.com/user-attachments/assets/174a7c33-4ef1-4c2a-932e-9a7cf4715561" />~~
-
 Thanks to the MakeCode Team that made the web editor.
 
-
-~~**Disclaimer:  Proceed with caution when performing technical procedures related to software extensions, as incorrect steps may result in data loss or application errors.**~~
-
-**You can find a blog about this here.** [pxt-hardware-programming-docs-issue-request](https://askkesny.blogspot.com/?page=en-git-developertryingtocodelikeotherofthem-pxt-hardware-programming-docs-1772682036803)
+**You may wish to find a blog about this here.** [pxt-hardware-programming-docs-issue-request](https://askkesny.blogspot.com/?page=en-git-developertryingtocodelikeotherofthem-pxt-hardware-programming-docs-1772682036803)
 
 
 ## Patience for this repository