Hi.
Based on the most formal definition and description of the Repository pattern in Martin Fowler's "Patterns of Enterprise Application Architecture" (Addison Wesley, 2003), it would be better to use the term "Wrapper/Adapter" pattern instead of "Repository".
The true "Repository" is a mediator, and its duty is just fetching data, not persisting.
However, your version is merely a wrapper around a complex composite class (EF DbContext) that acts as a facade behind the scenes.
Many computer science students and software developers are misguided by this documentation because Microsoft is a giant tech company, and they believe every word of Microsoft documentation as if it were told by God.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 8be69079-b229-819b-0408-fb6c6aa30b88
• Version Independent ID: 3657bdb9-00c1-bb97-3470-d4f8c7569676
• Content: Implementing the infrastructure persistence layer with Entity Framework Core
• Content Source: docs/architecture/microservices/microservice-ddd-cqrs-patterns/infrastructure-persistence-layer-implementation-entity-framework-core.md
• Product: dotnet-architecture
• Technology: microservices
• GitHub Login: @jamesmontemagno
• Microsoft Alias: jamont