Update README.md

README.md

@@ -32,9 +32,9 @@ My site's menu has some dynamicism including a search box, and was implemented a
 I do not like duplication, but in this case the trade-off is something I can live with. Maybe I will discover a better way. For instance, it is possible to embed blazor
 components in MVC views, so I could scrap the old one and use the blazor nav everywhere. 
 ## As long as you aren't working at uber-scale, you don't need to be too concerned about scalability ##
-First off: one server with 3 gigs of RAM has been shown to handle 5000 concurrent connections. Each user takes about ~273 KB, depending on the size of your state (https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/server?view=aspnetcore-3.1). To me, that means this is usable for 90% of the sites in the world. 
+First off: one Standard D1 V2 instance on Azure with 3.5 GB of memory has been shown to handle 5,000 concurrent connections. Each user takes about ~273 KB, depending on the size of your state (https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/server?view=aspnetcore-3.1, https://devblogs.microsoft.com/aspnet/blazor-server-in-net-core-3-0-scenarios-and-performance/). To me, that means this is usable for 90% of the sites in the world. 
 
-If you are highly likely to operate at uber-scale, this is probably not the technology for you. But if you live in that world, you already know that most of those projects use open source stacks because they are so much cheaper at the highest level of scale. And you probably have a large team of co-workers who thinks about nothing but scale.
+If you are highly likely to operate at uber-scale, this is probably not the technology for you. But if you live in that world, you already know that most of those projects use open source stacks because they are so much cheaper at that level. And you probably have a large team of co-workers who thinks about nothing but scale.
 
 Also, there are interesting options for pushing Blazor Server even further. Azure has SignalR Server, which can hold all your websocket connections for you, decreasing the per-user server load significantly.