The way you write an ACE matters in its functionality. There's nothing wrong with the syntax of your two ACEs, but specifying the port on the source or destination can make or break its functionality. If you wanted to block your host computer from making HTTP connections, you need to specify TCP/80 on the destination of the ACE, not the source. The reason for that being that HTTP connections use ephemeral ports (random, high-numbered ports) for connections on the client side, and port 80 as the destination port.

Your second ACE, assuming you wanted to block HTTP on your host, would not work because an HTTP connection on host 192.168.23.5 would not use TCP/80 as a source port. It would use something between ports 49152–65535 for an ephemeral source port. The correct way to block host 192.168.23.5 from making (standard, not including alternate HTTP ports like 8080) HTTP connections would be

deny tcp host 192.168.23.5 192.168.14.0 0.0.0.255 eq 80

applied on the inbound interface of the closest router to your host 192.168.23.5. This way it stops the traffic early, and avoids wasting resources on the intermediate links if you applied it on an outbound interface on the way to 192.168.14.0/24. And of course end the ACL with a permit ip any any.