From 7c34ac20271928d7452a08e9f4946926d5a36e46 Mon Sep 17 00:00:00 2001 From: Maryam Ziyad Date: Tue, 2 Apr 2024 08:39:05 +0530 Subject: [PATCH] Fix a typo --- .../interface-to-external-code/interface_to_external_code.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/interface-to-external-code/interface_to_external_code.md b/examples/interface-to-external-code/interface_to_external_code.md index a0b6cb9298..e47e3f893c 100644 --- a/examples/interface-to-external-code/interface_to_external_code.md +++ b/examples/interface-to-external-code/interface_to_external_code.md @@ -1,7 +1,7 @@ -# Interface to exteral code +# Interface to external code Ballerina supports interfacing to external code. This can be done by using the `external` keyword, instead of implementing the function body. The implementation figures out how to map to the external implementation. As part of interfacing to an external implementation, Ballerina supports another basic type called `handle`. The `handle` type is basically an opaque handle that can be passed to and from external functions. There is no typing for `handle` and it can be added as a private member of a Ballerina class for better type safety. ::: code interface_to_external_code.bal ::: -::: out interface_to_external_code.out ::: \ No newline at end of file +::: out interface_to_external_code.out :::